ci: unified crates.io release workflow using release-plz #78
Conversation
This file contains 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
popzxc
reviewed
Dec 5, 2024
antonbaliasnikov
force-pushed
the
aba-unified-release-pipeline
branch
from
0a462ad to
1c24b66
Compare
|
@popzxc , I also checked that the bot user has the correct permissions for this repository, so we can proceed with the merge and the final stage of testing. |
popzxc
previously approved these changes
Dec 5, 2024
|
Some more fixes are in progress. |
antonbaliasnikov
force-pushed
the
aba-unified-release-pipeline
branch
from
580bbbe to
5d9a2f3
Compare
popzxc
approved these changes
Dec 6, 2024
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.
Overview
Use a common unified CI for Rust release using release-plz.
Details
release-pleaseworkflow as it creates a release PR with expected changes, monitors next semver, updates changelogs etc. but it's more specialized for Rust packages because it supportscrates.iopublishing out of the box, additional breaking API checks usingcargo-semver-checks, easier to configure and support (for example, only one workflow file instead of two).release-plz.tomlfile in the workspace root. Comments added to each line to explain what each setting does.Current restrictions
As
release-plzdoes not provide the same output context asrelease-please, notifications for successful releases are not sent yet in the same format. It would require refactoring of theformat-release-please-for-slack-actionor simplier, just use GitHub release notifications in Slack that will not require any set up.