feat: use shared autorelease workflow #17
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
Member
Author
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
rswanson
requested review from
Evalir,
dylanlott and
prestwich
as code owners
prestwich
approved these changes
Nov 5, 2024
Evalir
approved these changes
Nov 5, 2024
Member
Author
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.
TL;DR
Simplified the auto-release workflow by utilizing a reusable workflow from init4tech/actions.
What changed?
Replaced the custom release verification and creation logic with a standardized reusable workflow. The new workflow maintains the same trigger conditions (pushing to main branch with changes to Cargo.toml) while reducing complexity.
How to test?