Repository navigation
Release MCP 0.3.0 and fix dependency audit failures - #19
Merged
Merged
Conversation
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
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.
The merged Figma integration still reported version 0.2.0, which is already published on npm, and main CI failed its runtime dependency audit. This prepares release 0.3.0 by refreshing the affected lockfile dependencies, raising the Zod minimum to 4.6.7, and aligning the npm, plugin, registry and runtime versions. It also documents the two Figma tools and separates verified publication history from pending releases.
Validation: npm run check passes (type checking, all 39 tests, build); npm audit --omit=dev --audit-level=high reports zero vulnerabilities; npm pack --dry-run passes and includes only the expected 27 package files. Local validation used Node 22.19.0; repository CI covers Node 22 and 24.
Rollout retains the existing domain, SQLite volume and encryption key. The matching Venusaur API and Charizard must be deployed before MCP. npm, registry and directory publication remain separate steps after deployment checks.