chore(release): sync package.json to v1.10.0#74
Merged
Conversation
Sync package.json with npm — v1.10.0 was already published by a prior CI run that failed to commit the version bump back to main. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
François (Lp-Francois)
approved these changes
May 11, 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.
Summary
latestContext
A prior CI run published 1.10.0 to npm but branch protection prevented it from committing the version bump back to main. A subsequent release then bumped to 1.9.1 (patch from 1.9.0). This leaves main out of sync — the next
feat:merge would try to publish 1.10.0 again and fail.This PR syncs the version so the next release correctly produces 1.11.0.
🤖 Generated with Claude Code