CI: add job to automate crate version bumping PR #8365
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
|
As per my last discussion with Christian, the project's current preference is to manually update these crate versions whenever needed. @cdecker, could you please elaborate your reason for posterity? Or if you would like to reconsider, I can proceed with reviewing the PR. |
|
Keep in mind that this will only automatically create a PR to bump versions, not push to master directly. |
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.
I want these to go out faster after a CLN release so here's a github action that will automatically create a PR (like daywalker90#20) to bump crate versions very similar to the python action. It works for rc, major and minor releases. Merging that PR will trigger the other action to publish them.
Please check that the Workflow permissions under "Settings->Actions->General" are "Read and Write Permissions" aswell as "Allow GitHub Actions to create and approve pull requests".
For this i had to centralize the version management of the affected crates.