ci: migrate release automation to release-please#3
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.
Re-open of the release-please migration against
main.PR #2 was accidentally merged into
feat/quality-toolinginstead ofmain(its base wasn't retargeted before merge), so the migration never reachedmain— it still had the old git-cliffrelease.ymland norelease-please.yml. This PR lands the migration onmain.Added
.github/workflows/release-please.yml— runs on push tomain.release-please-config.json— single package.,release-type: python,bump-minor-pre-major..release-please-manifest.json— seeded with0.2.0.Removed
.github/workflows/release.yml(git-cliff) andcliff.toml.Updated
pyproject.toml([tool.commitizen]scoped to commit-msg validation),README.md,docs/WORKFLOW.md.Workflow permissions ("Read and write" + "Allow GitHub Actions to create and approve pull requests") are already enabled, so on merge release-please should open the first release PR on the next push to
main.