Ensure package.json version gets updated on release #51
+1
−1
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
|
BTW, i can't merge this any more :( |
|
@bruderstein long time no see! thanks for being on top of things always ❤️ I hope all is well on the other side 🙂 |
|
thanks dave, hope you are doing well! |
|
🎉 This PR is included in version 3.1.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
lukehorvat
added a commit
that referenced
this pull request
Feb 17, 2023
intervene-ci
pushed a commit
that referenced
this pull request
Feb 17, 2023
## [3.1.4](v3.1.3...v3.1.4) (2023-02-17) ### Bug Fixes * Use semantic-release plugin defaults so that fix from [#51](#51) works ([8bd5b77](8bd5b77))
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.
The version in package.json has been stuck on 3.0.1 for a while and is not in sync with the version in the npm registry. It doesn't really matter, but I thought I'd fix anyway.
It seems we need to swap the order of the semantic-release plugins,
npmandgit. See: semantic-release/semantic-release#1593 (comment)