CI: auto-release a version tag when Renovate merges a dependency update #16
Reference in New Issue
Block a user
Delete Branch "auto-release"
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?
Auto-cuts a
vX.Y.Zrelease tag when Renovate merges a dependency update, so image releases track dependency changes without manual tagging.apiVersion. Amajorrelease is just a bigger image tag;HOST_API_VERSION(the plugin contract) is untouched and never breaks plugins for a dep bump.renovate.jsonstamps each commit with aRelease-Bump: {{{updateType}}}trailer.renovate.ymlgains anauto-releasejob (needs: renovate) that targetsorigin/main, and — when the tip is a Renovate commit with untagged changes — computes the next tag (highest trailer since the last tag; pre-1.0 shifts down so nothing auto-crosses into1.0.0) and pushes it with renovate-bot's PAT sorelease.ymlpromotes the already-built image.auto-release/next-version.tsis a pure, unit-tested core (0.x-preserving semver).Verified:
renovate-config-validator --strict,tsc --noEmit, 376 unit tests (5 new); the tag/trailer/empty-range/human-tip git plumbing exercised in scratch repos. Stability-reviewer approved.