ci: automate releases with release-please - #18
Merged
Conversation
Replaces manual git tag creation with a release-please workflow that opens a PR bumping build.gradle's version and CHANGELOG.md from conventional commits. Merging that PR creates the tag the same way a manual tag push does today, so docker-image.yml's deploy_production trigger is unchanged. Requires a repo secret RELEASE_PLEASE_TOKEN (fine-grained PAT with Contents: RW and Pull requests: RW) so the resulting tag push is not treated as a GITHUB_TOKEN-originated event, which GitHub Actions would otherwise ignore for triggering downstream workflows.
Dry-run testing on ci/release-please-automation confirmed the config works (opened PR #17 bumping 2.3.0 -> 2.3.1). Switching the trigger and target-branch back to main so release-please runs for real once this branch is merged. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lb9CYCBEdjtBtyzyFv4N6Q
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
simpleand version tracked inbuild.gradlevia the manifest.ci/release-please-automationwith a matchingtarget-branch) — confirmed it correctly reads history since the2.3.0tag and opens a well-formed release PR (see chore(ci/release-please-automation): release 2.3.1 #17, which can be closed once this merges).target-branchfrom the test branch tomainfor production use.Test plan
chore(...): release 2.3.1) with correct changelog and version bumpmaintriggersrelease-pleaseand opens a real release PR againstmainmain-targeted PR appears🤖 Generated with Claude Code
https://claude.ai/code/session_01Lb9CYCBEdjtBtyzyFv4N6Q