ci: Use release-please for release creation #7279
Open
+48
−0
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
c-warren
requested review from
Shaddoll,
neil-xie,
davidporter-id-au,
Groxx,
shijiesheng,
jakobht,
3vilhamster,
sankari165,
dkrotx,
taylanisikdemir and
demirkayaender
as code owners
davidporter-id-au
approved these changes
Sep 30, 2025
natemort
reviewed
Sep 30, 2025
.release-please-config.json
Outdated
| {"type": "refactor", "section": "Code Refactoring"}, | ||
| {"type": "test", "section": "Tests"}, | ||
| {"type": "build", "section": "Build System"}, | ||
| {"type": "ci", "section": "Continuous Integration"} |
There was a problem hiding this comment.
Nit: I'd maybe just keep feat/fix/perf, I don't know if these other ones add a lot of value
natemort
approved these changes
Sep 30, 2025
|
This is waiting until we can update the GitHub settings to allow actions (like release-please) to create PRs/update tags. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why?
Our existing commit process:
Furthermore, users have stated that our release notes do not provide easily discernable information about what is in a release, including:
Adding conventional commits aims to tackle these pieces and make contributing to the repository significantly easier.
This PR adds release please that will automate some of the release process. It relies on conventional commits being used, so will only become valuable once that starts to happen.
How did you test it?
Currently testing.
Potential risks
Adding this GitHub action may have unintended consequences for the commit process, and should be monitored to ensure that it doesn't inhibit merging to the repository.
Release notes
N/A
Documentation Changes