ci: add release-please#57
Merged
Merged
Conversation
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.
Brings
docs-argocdonto the GlueOps-standard release-please setup. Previously there was no release automation — tags/releases (latestv0.19.0) were cut manually. This wires up automated version bumps + changelog via Conventional Commits.What this adds
.github/workflows/release-please.yaml— runs on push tomain, authenticates via thepublic-release-pleaseGitHub App (actions/create-github-app-token), and maintains a release PR.release-please-config.json— manifest mode with:release-type: simple(tracksversion.txt; repo is a Terraform module + argocd template, not Node/Go/Helm)include-component-in-tag: false→ plainvX.Y.Ztags (matches existing tag format)bump-minor-pre-major: true(0.x repo — a breaking change bumps the minor, not to 1.0.0)changelog-sections(all Conventional-Commit types visible).release-please-manifest.json— seeded to0.19.0(the latest existing tag) so releases continue from there.No container image is published (no
Dockerfile), so no image-build workflow was added.After merge
The next
feat:/fix:commit onmainopens a release PR; merging that release PR cuts the release +vX.Y.Ztag.The org secret
RELEASE_PLEASE_APP_PRIVATE_KEYmust be visible to this (public) repo — visibility All repositories (or Selected incl. this repo). Could not verify via API (requires org admin), but other GlueOps repos run release-please fine, so this is likely already set.🤖 Generated with Claude Code