Repository navigation
fix(cd): tags/branches named vX.Y.Z, not [email protected] - #4
Merged
Merged
Conversation
…[email protected] cargo pkgid -p funera-core prints '[email protected]', so sed 's/.*#//' produced branch release/[email protected] and would have pushed tag [email protected] and created a release with the same name. Use cargo metadata + jq to get the bare version in the PR/tag/release steps.
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
1 participant
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.
The release steps extracted the version with \cargo pkgid ... sed 's/.*#//', which yields \ [email protected]\ (package name included). That produced the branch
elease/[email protected]\ and would have pushed tag / created release \�[email protected]. Use \cargo metadata\ + \jq\ so the tag, branch, PR title, and release are all \�0.3.0.