Bump version to 0.2.5#19
Merged
Merged
Conversation
The v0.2.5 release tag was published against a commit where package.json was still 0.2.4, so the publish workflow's version guard aborted before pushing to npm. Bump the version so the tag matches.
|
Consistent version bump to 0.2.5. 🎯 Quality: 75% Good · 📦 Size: Tiny 📈 This month: Your 102nd PR — above team average · Averaging Excellent |
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.
Summary
package.jsonandpackage-lock.jsonfrom0.2.4to0.2.5.Context
The
v0.2.5GitHub Release (deployment) was published against a commit wherepackage.jsonwas still0.2.4. The publish workflow's version guard (publish.yml:54-56) correctly aborted before pushing to npm, so@patchstack/connect@0.2.5was never published.After merge, the existing
v0.2.5tag and Release will be deleted and re-created on the merged commit so the publish workflow can run cleanly.Test plan
v0.2.5release/tag and confirm the publish workflow succeeds