Repository navigation
chore(release): promote version - #406
Merged
Merged
Conversation
Promote the 1.0 release candidates to stable: core, components, react and lit 1.0.0; mcp 1.0.2; react-mcp-stack and lit-mcp-stack 1.0.1. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
yia-mw-agent
approved these changes
Nov 5, 2026
yia-mw-agent
left a comment
yia-mw-agent
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the full merge-base-to-head diff (base main aa370a6 = merge-base, 8 files, version values only) at 3d4c58a.
- All seven versioned packages move to their promoted versions (core/components/react/lit 1.0.0, mcp 1.0.2, react-mcp-stack/lit-mcp-stack 1.0.1). Sibling pins in dependencies, peerDependencies and devDependencies mirror those exact versions, with no stale rc pin left in any package.json.
- package-lock.json changes match the manifests;
npm cisucceeds on the head. python3 scripts/mw-version.py check --base origin/main --title 'chore(release): promote version'passes, and the version-enrollment check passes.tsc --noEmitpasses for all seven packages. The rootnpm run typecheckstopped at a missing@lynx-js/types, which comes from the separate apps/lynx-fixture install I did not perform here. The diff touches no code, so I treat this as environmental.- The remote Version policy check passes. Two other checks were still pending when I looked.
Non-blocking: docs/build-tic-tac-toe-with-react.md, docs/tic-tac-toe/1-first-card.md and docs/tic-tac-toe/checkpoints/first-card.md still pin @saga-a2ui/react-mcp-stack to 1.0.0-rc.1. That is out of scope for a version-values-only PR and the rc stays installable, but you may want a follow-up to point them at the stable line.
No material defects.
Helmet-Review-Request: #406 (comment)
This branch was successfully deployed
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.
Promotes the saga a2ui 1.0 release candidates to the stable 1.0 line. Only version values change.
@saga-a2ui/core,components,react,lit1.0.0@saga-a2ui/mcp1.0.2@saga-a2ui/react-mcp-stack,lit-mcp-stack1.0.1The rc changes since 1.0.0-rc.1 are #404 (a required view
majorandz3only) and #405 (the 413 reaches a Node client).Checks
mw-version.py checkwith this title: version policy passes, and sibling pins mirror the promoted versions exactly.npm run typecheck: passes.🤖 Generated with Claude Code