Backfill Releases for the Images already published #51

Closed
opened 2026-10-10 11:33:30 +00:00 by piscis · 0 comments
Owner

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.

  • The release script from #48 gets a post mode. It creates the Release with Forgejo's create-release endpoint, passing the tag name (equal to the Image tag, no v prefix) and the target commit, so Forgejo creates the tag itself.
    • No git push, no changelog file.
    • If the tag already has a Release, it creates nothing and exits successfully.
  • Run it once for every Rebuild already published without a Release: 3.2.0-r1, plus 3.2.0-r2 if #46 has published by then. Each Release's tag targets the commit in that Image's org.opencontainers.image.revision label. The oldest Release's notes run from the start of the history.

Acceptance criteria

  • Each published Image tag has a Release with the same name
  • Each Release's git tag targets the commit in its Image's revision label
  • Running the post mode again creates no duplicate and exits successfully
  • The backfilled notes skip non-conventional merge commits but keep the conventional commits inside them

Blocked by

## 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. - The release script from #48 gets a post mode. It creates the Release with Forgejo's create-release endpoint, passing the tag name (equal to the Image tag, no `v` prefix) and the target commit, so Forgejo creates the tag itself. - No git push, no changelog file. - If the tag already has a Release, it creates nothing and exits successfully. - Run it once for every Rebuild already published without a Release: `3.2.0-r1`, plus `3.2.0-r2` if #46 has published by then. Each Release's tag targets the commit in that Image's `org.opencontainers.image.revision` label. The oldest Release's notes run from the start of the history. ## Acceptance criteria - [ ] Each published Image tag has a Release with the same name - [ ] Each Release's git tag targets the commit in its Image's revision label - [ ] Running the post mode again creates no duplicate and exits successfully - [ ] The backfilled notes skip non-conventional merge commits but keep the conventional commits inside them ## Blocked by - #48
Sign in to join this conversation.
No description provided.