feat(ci): cut a Release for every published Image #54
No reviewers
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.
Dependencies
No dependencies set
Reference
vicoli-oss/docker-forgejo-mcp!54
Loading…
Reference in a new issue
No description provided.
Delete branch "piscis/releases"
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?
Summary
Base images are tracked and guarded, and every published Image gets a Release named like its Image tag.
fix(deps): update base images, with digest + minor (no major) for Go. Its notes tell the reviewer to raise the Rebuild; the guard fails it until they do.secrets.RELEASE_TOKEN || github.token. Forgejo v16's source gives a task token write on its own repo with no scope limits, so the automatic token should be enough; the first dispatch on main confirms it (seedocs/agents/forgejo.md).3.2.0-r1, tag on7f2e214, the revision label of that Image. A second post run created nothing.Evidence
acf3b4e(distroless digest dropped, Pin unchanged), reverted in0424bba, failed CI run 6162:Cut a Release for every published Imagestarted run 6164, which failed withcheck-title: FAIL: '…' is not a Conventional Commit. Restoring it started run 6165, green, without a push.3.2.0-r1tag,make release-notesprints:v3.2.0 … unchanged since 3.2.0-r1,Rebuild: 2, Bug fixesBuild the Image with Go 1.27, as Go 1.25 is out of support; #43 and #44 (scripts) are left out. On CI's dind the preview targets7f2e214from the registry label.forgejo-mcp. After: it detectsgolangandgcr.io/distroless/static-debian12in branchrenovate/base-images, titledfix(deps): update base images; the Pin PR stayschore(deps): update upstream forgejo-mcp to ….Merge Danger
Door: two-way, except for Releases: each push to main that publishes a new Image tag creates a Release and a git tag, which stay unless deleted by hand.
Blast Radius: CI
PRs that change a base image without a Rebuild, or carry a non-conventional title (a
WIP:draft included), now fail. If the automatic token can't create Releases, the release step on main fails after publishing; the Image is still published, and addingRELEASE_TOKENthen re-running repairs it.Closes #47
Closes #48
Closes #49
Closes #50
Closes #51
Closes #52
feat: cut a Release for every published Imageto Cut a Release for every published ImageCut a Release for every published Imageto feat: cut a Release for every published Imagefeat: cut a Release for every published Imageto feat(ci): cut a Release for every published Image- release-test.sh exited 0 untested when run without make: ${VAR:?} under the EXIT trap. Both scripts now check with [ -n … ] || fail, as docs/agents/releases.md says. - release.sh asks the registry for the same manifest types as publish.sh. - usage() prints the header's Usage block by its markers, not by line numbers. - IMAGE_REPO's default notes that it must match ci.yml.