Repository navigation
chore: release v2.3.0 - #231
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.
Bumps framesmith to 2.3.0 in
package.json,package-lock.json, and theversionthe MCP server reports insrc/index.ts.This is a minor release because
canvas_bindgains a new field in its result. Everything else is a fix or a documentation correction.batch_designaccepts an op written across several lines, as long as its brackets are still open. It also accepts#comment lines between ops and//comments at the end of a line. Before, the README's own chart, donut and intro examples failed when pasted as written. A#or//inside a quoted string is not treated as a comment. A paren or brace inside a string value no longer breaks an op either; before, that failed even on a single line.canvas_bindreturns anidMapthat maps the old workspace and project IDs to their newrepo-*IDs, so an agent can retarget without listing again. The docs used to say binding changes canvas IDs too. It doesn't: canvas IDs are kept, and each canvas'sprojectIdis updated to its new project. Every place that made the claim is corrected.An agent can newly see two things: multi-line ops and comments in
batch_design, and theidMapfield in thecanvas_bindresult. No existing field changes.npm run buildsucceeds,npm run test:fastpasses (72/72),test-discoverability.tspasses (117/117), andnpm pack --dry-runreports version 2.3.0 with 115 files.