Publish latest only for releases, main for the branch tip, and show the running version closes #561 #654
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!654
Loading…
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-561"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #561, closes #506
Description of the implemented changes
The changes were:
Releases and image tags:
latestpoints to the newest release andmainto 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?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
latestno longer follows main. An installation pullinglatestmoves to 1.4.0 on its next update. To keep following main, it has to switch tomain(README "Container images and tags").ci/promote-image.sh(crane). The tag must be on main, andmix.exs,publiccode.ymland the changelog must agree (mix mv.release.check).FORGEJO_RELEASE_TOKEN(docs/releasing.md).Mv.Release.Versioning,Mv.Release.Files, four mix tasks, tests)..drone.jsonnet, the promote script and its stub-crane test)..tags;docker buildplusdocker inspectof the labels and env;