chore(release): 1.9.2 - #130
Merged
Merged
Conversation
1.9.1 declares @fozikio/reflex ^0.2.0, so every fresh install still gets reflex 0.2.1. In that version the path-traversal CORE_RULE hard-blocks any command containing '..' (Fozikio/reflex#6). #127 moved master to ^0.3.0, but consumers only get the fix from a release. The @modelcontextprotocol/sdk floor goes to ^1.30.1 as well, so the /mcp endpoint is guaranteed the SDK's request-body and batch-length limits rather than only getting them when the lockfile happens to resolve there. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Patch release. Published 1.9.1 declares
@fozikio/reflex ^0.2.0, so fresh installs still resolve reflex 0.2.1, where thepath-traversalCORE_RULE hard-blocks any command containing..(Fozikio/reflex#6). This was verified with a temp-dir install on 2026-09-28. Master moved to^0.3.0in #127; this release is what gets that fix to consumers.@modelcontextprotocol/sdkfloor →^1.30.1(server-side request-body and batch-length limits, relevant to/mcp). The lockfile is hand-edited to three lines only, because local npm 11 dropslibcfields.local-cipassed on 8d2d9e4: 431/431 tests, 0 vulnerabilities.verify:packageis clean. After merge, pushing tagv1.9.2publishes via OIDC.🤖 Generated with Claude Code