Skip to content

chore(plasmic-mcp): bump to 0.2.4 - #514

Merged
field123 merged 1 commit into
masterfrom
chore/plasmic-mcp-0.2.4
Aug 28, 2026
Merged

chore(plasmic-mcp): bump to 0.2.4#514
field123 merged 1 commit into
masterfrom
chore/plasmic-mcp-0.2.4

Conversation

@field123

Copy link
Copy Markdown
Collaborator

Releases the expression-parenthesization fix from #511 (#485).

package.json and manifest.json both move to 0.2.4. Both are required: the build fails if they disagree, because Claude Desktop reads the manifest while npm ships the package, and drift makes it impossible to tell which code a user has installed.

0.2.4 rather than 0.3.0 on the basis that this is a bug fix, but the judgement is arguable — the eight write sites it touches previously had no validation at all, so input that is not parseable JavaScript is now refused rather than stored broken, and a simple scope path is stored as an ObjectPath where it used to be a CustomCode.

Verified on this tree (detached origin/master + this commit): type-check clean, 2391 tests passing across 56 files, bundle builds at 3954.7 KB, and the packed tarball installed into an isolated directory reports v0.2.4, completes the MCP handshake, and lists all 10 tools.

Once merged, plasmic-mcp-v0.2.4 gets tagged on the merge commit, which triggers the .mcpb release, and the npm package is published from that tree.

@field123
field123 merged commit 747b0c8 into master Aug 28, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant