chore(release): bump version to 1.0.17#210
Merged
Merged
Conversation
v1.0.16 release failed to publish because package.json was still at 1.0.15 (npm rejects publishing over an existing version). 1.0.16 was never published to npm; moving forward to 1.0.17 instead of rewriting the immutable v1.0.16 tag/release. Co-authored-by: GitHub Copilot <copilot@noreply.github.com>
marcelo-staffbase
approved these changes
Jun 23, 2026
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
2 participants
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.
Problem
The
v1.0.16release failed to publish to npm:The
v1.0.16tag/release was cut, butpackage.jsonwas never bumped — it still read1.0.15, which is already on npm. Sonpm publishrefused to overwrite it.Fix
Bump
package.jsonto 1.0.17.1.0.16was never published to npm, but versions/tags are immutable, so we move forward to1.0.17rather than rewriting the existingv1.0.16tag and release.Follow-up after merge
Cut a fresh
v1.0.17release (thePublish to NPM Registryworkflow triggers onrelease: created) to publish to npm.Co-authored-by: GitHub Copilot copilot@noreply.github.com