Automate version bumps and tagging with release-please#8
Merged
Merged
Conversation
PR merges to main now feed a standing release-please PR that decides the next semver bump from Conventional Commits and, on merge, creates the vX.Y.Z tag - replacing manual tagging. release.yml is unchanged: it still triggers off that tag and still gates publishing behind manual approval. skip-github-release avoids a duplicate Release object since release.yml's publish job already creates one. Requires a RELEASE_PLEASE_TOKEN repo secret (fine-grained PAT, Contents: read/write) - the default GITHUB_TOKEN can't be used here since GitHub blocks its pushes from triggering other workflows.
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.
PR merges to main now feed a standing release-please PR that decides the next semver bump from Conventional Commits and, on merge, creates the vX.Y.Z tag - replacing manual tagging. release.yml is unchanged: it still triggers off that tag and still gates publishing behind manual approval. skip-github-release avoids a duplicate Release object since release.yml's publish job already creates one.
Requires a RELEASE_PLEASE_TOKEN repo secret (fine-grained PAT, Contents: read/write) - the default GITHUB_TOKEN can't be used here since GitHub blocks its pushes from triggering other workflows.
What and why
Checklist
dotnet test)dotnet format --verify-no-changespassesCHANGELOG.mdupdated under[Unreleased]docs/COMPATIBILITY.mdupdated for any endpoint you implemented or changed