Backfill Releases for the Images already published #51
Labels
No labels
bug
enhancement
needs-info
needs-triage
ready-for-agent
ready-for-human
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#52 CI cuts a Release for every published Image
vicoli-oss/docker-forgejo-mcp
#48 Preview the notes of the next Release locally
vicoli-oss/docker-forgejo-mcp
Reference
vicoli-oss/docker-forgejo-mcp#51
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Parent
#45
What to build
The Releases page starts complete. Every Image already published has a Release named exactly like its Image tag, so the first automated Release's notes don't contain the repo's whole history.
vprefix) and the target commit, so Forgejo creates the tag itself.3.2.0-r1, plus3.2.0-r2if #46 has published by then. Each Release's tag targets the commit in that Image'sorg.opencontainers.image.revisionlabel. The oldest Release's notes run from the start of the history.Acceptance criteria
Blocked by