Repository navigation
Conversation
Replace tag-triggered releases with release-please. Merging the release PR creates a draft release, and the workflow attaches the binaries, checksums and signature before publishing it, since immutable releases reject uploads after publication. Renovate now uses fix(deps) for dependencies that ship in the binary or image, so their updates cut a release. Release-As: 0.8.1 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replace tag-triggered releases with release-please.
release.ymlruns on pushes tomain. release-please keeps a release PR open; merging it creates a draft release (withforce-tag-creation, so the tag exists immediately). The existing build / checksums / cosign / attest / GHCR jobs then run, and the release job uploads the assets and publishes the draft. Immutable releases reject uploads after publication, so the assets must be attached while the release is still a draft.actions/create-github-app-token), because a release PR opened withGITHUB_TOKENdoes not trigger CI. Its credentials come from thereleaseenvironment, which only push runs enter.tag_name(value=), since the run is no longer triggered by a tag push.:semanticCommitTypeAll(chore)to:semanticPrefixFixDepsChoreOthers, so dependency updates that ship in the binary or image usefix(deps)and cut a patch release.cmd/dockerflagsgendependencies staychore, and Go toolchain updates (godirective,golangimage) becomefix.Before merging
googleapis/release-please-actionmust be in the repository's allowed actions.releaseenvironment holds the App'sRELEASE_PLEASE_CLIENT_ID(variable) andRELEASE_PLEASE_PRIVATE_KEY(secret). The App needs Contents, Issues and Pull requests read & write.Release-As: 0.8.1footer in the squash commit message, so the first release PR is for 0.8.1 (the commits since v0.8.0 are allchore/ciand would not cut a release otherwise).Testing
actionlintonrelease.yml: no findings apart fromubuntu-slimandcache-mode, which that actionlint version does not know yet.renovate-config-validator: config validated successfully.release.ymlexercises the build and docker jobs without publishing.🤖 Generated with Claude Code