ci: change version change check in release workflow + re-trigger release commit #423
Conversation
This file contains 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
Release-As: 0.25.0
| - name: 📦 Publish to NPM | ||
| if: env.SHOULD_RELEASE == 'true' | ||
| if: steps.release.outputs.releases_created |
There was a problem hiding this comment.
Hmm, nice. So only feat:, fix: or BREAKING CHANGE: will create a release, right?
There was a problem hiding this comment.
no pushing a commit pattern like below can create a release manually too
JeneaVranceanu
approved these changes
Apr 18, 2024
Hugoo
approved these changes
Apr 18, 2024
richtera
approved these changes
Apr 18, 2024
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.
Release-As: 0.25.0
What kind of change does this PR introduce (bug fix, feature, docs update, ...)?
Remove the outdated version check step and use the release-please output instead.