Publish latest only for releases, main for the branch tip, and show the running version closes #561 #654

Merged
simon merged 11 commits from issue/mitgliederverwaltung-561 into main 2026-11-10 10:39:56 +01:00
Owner

closes #561, closes #506

Description of the implemented changes

The changes were:

  • Bugfixing
  • New Feature
  • Breaking Change
  • Refactoring

Releases and image tags: latest points to the newest release and main to the head of main. A release reuses the image main tested and gets a draft release in Forgejo. Administrators see the running version and commit in the settings.

What has been changed?

  • Record 1.4.0 as the current version
  • Keep mix.exs, publiccode.yml and the changelog on one release version
  • Carry the version and commit into the image and the running app
  • Show the running version and commit to admins
  • Publish latest only for the newest release and main for the branch tip
  • Draft a Forgejo release with the changelog section for each tag
  • Recommend an image tag per audience and describe the release steps
  • Promote the tested main image for a release instead of rebuilding it
  • Record the version in the settings, the main and release image tags and the new meaning of latest under Unreleased

Definition of Done

Code Quality

  • No new technical depths
  • Linting passed
  • Documentation is added were needed

Accessibility

  • New elements are properly defined with html-tags
  • Colour contrast follows WCAG criteria
  • Aria labels are added when needed
  • Everything is accessible by keyboard
  • Tab-Order is comprehensible
  • All interactive elements have a visible focus

Testing

  • Tests for new code are written
  • All tests pass
  • axe-core dev tools show no critical or major issues

Additional Notes

  • Breaking for operators: latest no longer follows main. An installation pulling latest moves to 1.4.0 on its next update. To keep following main, it has to switch to main (README "Container images and tags").
  • The tag pipeline builds nothing. It waits up to 30 minutes for the image main published for the tagged commit, checks that the image's revision label matches the commit, and adds the release tags with ci/promote-image.sh (crane). The tag must be on main, and mix.exs, publiccode.yml and the changelog must agree (mix mv.release.check).
  • The draft release needs the Drone secret FORGEJO_RELEASE_TOKEN (docs/releasing.md).
  • The two publishing pipelines no longer restore the shared build cache. Each main build compiles from scratch.
  • Every step image in the publishing pipelines is pinned by digest.
  • Larger commits:
    • "Keep mix.exs, publiccode.yml and the changelog on one release version" (Mv.Release.Versioning, Mv.Release.Files, four mix tasks, tests).
    • "Promote the tested main image …" (.drone.jsonnet, the promote script and its stub-crane test).
  • CI wiring cannot be tested in ExUnit. It was checked locally instead:
    • the rendered jsonnet;
    • a plugins/docker dry run reading .tags;
    • docker build plus docker inspect of the labels and env;
    • the promote script against a local registry, where layers stayed identical, all tags shared one digest and a foreign revision was refused.
closes #561, closes #506 ## Description of the implemented changes The changes were: - [x] Bugfixing - [x] New Feature - [x] Breaking Change - [ ] Refactoring Releases and image tags: `latest` points to the newest release and `main` to the head of main. A release reuses the image main tested and gets a draft release in Forgejo. Administrators see the running version and commit in the settings. ## What has been changed? - Record 1.4.0 as the current version - Keep mix.exs, publiccode.yml and the changelog on one release version - Carry the version and commit into the image and the running app - Show the running version and commit to admins - Publish latest only for the newest release and main for the branch tip - Draft a Forgejo release with the changelog section for each tag - Recommend an image tag per audience and describe the release steps - Promote the tested main image for a release instead of rebuilding it - Record the version in the settings, the main and release image tags and the new meaning of latest under Unreleased ## Definition of Done ### Code Quality - [ ] No new technical depths - [x] Linting passed - [x] Documentation is added were needed ### Accessibility - [ ] New elements are properly defined with html-tags - [ ] Colour contrast follows WCAG criteria - [ ] Aria labels are added when needed - [ ] Everything is accessible by keyboard - [ ] Tab-Order is comprehensible - [ ] All interactive elements have a visible focus ### Testing - [x] Tests for new code are written - [ ] All tests pass - [ ] axe-core dev tools show no critical or major issues ## Additional Notes - Breaking for operators: `latest` no longer follows main. An installation pulling `latest` moves to 1.4.0 on its next update. To keep following main, it has to switch to `main` (README "Container images and tags"). - The tag pipeline builds nothing. It waits up to 30 minutes for the image main published for the tagged commit, checks that the image's revision label matches the commit, and adds the release tags with `ci/promote-image.sh` (crane). The tag must be on main, and `mix.exs`, `publiccode.yml` and the changelog must agree (`mix mv.release.check`). - The draft release needs the Drone secret `FORGEJO_RELEASE_TOKEN` (`docs/releasing.md`). - The two publishing pipelines no longer restore the shared build cache. Each main build compiles from scratch. - Every step image in the publishing pipelines is pinned by digest. - Larger commits: - "Keep mix.exs, publiccode.yml and the changelog on one release version" (`Mv.Release.Versioning`, `Mv.Release.Files`, four mix tasks, tests). - "Promote the tested main image …" (`.drone.jsonnet`, the promote script and its stub-crane test). - CI wiring cannot be tested in ExUnit. It was checked locally instead: - the rendered jsonnet; - a plugins/docker dry run reading `.tags`; - `docker build` plus `docker inspect` of the labels and env; - the promote script against a local registry, where layers stayed identical, all tags shared one digest and a foreign revision was refused.
simon merged commit 85d4af3eb2 into main 2026-11-10 10:39:56 +01:00
Sign in to join this conversation.
No description provided.