Preview the notes of the next Release locally #48
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
#51 Backfill Releases for the Images already published
vicoli-oss/docker-forgejo-mcp
Reference
vicoli-oss/docker-forgejo-mcp#48
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
A maintainer can print the notes of the next Release locally, without creating anything. The notes are what CI will later post as the Release for the current Image tag.
make release-notesruns git-cliff as a digest-pinned container image, the same way the existing linters are run. No Node toolchain enters the repo.Header built from the Pin:
This covers Upstream bumps, which Renovate commits as
chore(deps)and which the commit groups would otherwise hide.Body: Conventional Commits groups for
feat,fix,perfand breaking changes since the previous Release.scripts,skills,renovate,agentsorciare skipped as repo-internal.image, affects Consumers and is included.Previous Release: the nearest earlier Release tag on the history of main (git ancestry), never semver ordering. As semver,
3.2.0-r10would sort before3.2.0-r2. With no Release tag yet, the notes run from the start of the history.The dry run prints the notes and the create-release request payload it would send: tag name equal to the Image tag (no
vprefix), and target commit.The agent docs list the internal scopes and the rule that a change with no scope, or scoped
image, shows up in Release notes.Acceptance criteria
make release-notesprints a header and notes for the Image tag frommake print-tag, and creates nothing3.2.0-r2and a local3.2.0-r1tag on that Image's revision, the notes contain the Go 1.27 fix and leave out #43 and #44, and the header shows v3.2.0, Rebuild 2, Upstream Version unchangedBlocked by
None (can start immediately).