Repository navigation
ci: make the release dry run touch nothing in the repository - #3
Merged
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
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.
Untick publish in the Release workflow and it now only works out the version, generates the changelog and runs
cargo publish --workspace --dry-runon the bumped tree, then stops. Nothing is committed, tagged, built, released or uploaded; the run summary shows the version and release notes.Before this, unticking publish skipped only the crates.io upload but still pushed the version commit and tag and created the GitHub release.
Checked: actionlint is clean; running the bump script with publish=false picked v0.3.0 from the commits and pushed nothing (no new tag or commit on origin).