chore: sync package-lock.json and CHANGELOG.md with v0.3.24 release#512
Merged
Conversation
PR #511 bumped only package.json, so the lockfile version fields and the changelog were left at 0.3.23 while the tag, GitHub release, and npm publish went out as 0.3.24.
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
1 participant
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
PR #511 bumped the version by editing only
package.json. The v0.3.24 tag, GitHub release, and npm publish all went out correctly via the Release workflow, but two files were left behind at 0.3.23:package-lock.json— both rootversionfields (top-level andpackages[""]) still said 0.3.23CHANGELOG.md— no 0.3.24 entry (previous releases vianpm run release/ standard-version updated all three files together)Changes
🤖 Generated with Claude Code