Repository navigation
ci: use prepared version for release pull request - #255
Merged
Merged
Conversation
Contributor
Coverage report
Test suite run success232 tests passing in 19 suites. Report generated by 🧪jest coverage report action from be2a82d |
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.
When release preparation is given an explicit version, the workflow currently calculates the PR branch, title, and commit message separately without those options. For example, #254 prepared 5.0.0 under a 4.11.0 title and branch.
Read the version from package.json after release-it prepares the changes so the PR metadata matches the actual release version.
Validation: checked workflow YAML and step order, verified reading a 5.0.0 package version, and ran the repository build, lint, and test hooks (232 tests passed). The workflow was not dispatched on GitHub.