chore(ci): add release-please for automated version + changelog management#2
Merged
Conversation
Add the release-please workflow + config + manifest, mirroring the same pattern used in nwarila-platform/proxmox-packer-framework and the nwarila-platform/secure-rockylinux9-template consumer repo. Update the allowlist-style .gitignore so the new files are tracked. How it works: - On push to main, the release-please action scans new conventional commits since the last tagged release. - For feat: / fix: / security: / refactor: / ci: / docs: it opens or updates a release PR titled "chore: release X.Y.Z" that bumps the manifest, regenerates CHANGELOG.md, and proposes the next version. - Merging that release PR creates the corresponding tag (with v prefix per include-v-in-tag), which in turn triggers Release Artifact (already wired on push: tags: v*) to build, attest, and publish the GitHub release with the bundle assets. Manifest baseline is 1.0.0 -- the existing tag. Next release is computed from conventional commits merged after the v1.0.0 tag (only chore(codeowners) right now, which is hidden from the changelog and does not bump versions, so no release PR will open until a feat/fix lands). This standardizes release management across all three repos in the secure Packer / Proxmox toolchain (framework, bootstrapper, consumer template). Co-Authored-By: Claude Opus 4.7 (1M context) <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
1 participant
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
Add release-please to standardize version + changelog management across the three repos in the secure Packer toolchain (
proxmox-packer-framework,secure-rockylinux9-template, and now this one).What this adds
.github/workflows/release-please.yaml— runs release-please on push to main.release-please-config.json—simplerelease-type, conventional-commit changelog sections matching the framework + consumer repos..release-please-manifest.json— baseline at1.0.0(the existing tag)..gitignoreallowlist updated for the three new files.How the chain works after this
feat:/fix:/ etc.).chore: release X.Y.Zthat regeneratesCHANGELOG.mdand bumps the manifest.vX.Y.Ztag.Release Artifactworkflow (already wired onpush: tags: v*) builds the bundle, attests provenance, and publishes the GitHub release with the assets the downstream consumer pin script consumes.Why no release PR will open immediately
The only commit on main since
v1.0.0ischore(codeowners): sync CODEOWNERS via terraform, which is hidden from the changelog and doesn't bump versions. So the workflow runs cleanly but produces no PR until afeat:orfix:lands.Test plan
🤖 Generated with Claude Code