chore(release): reconcile main history into dev - #18
Merged
Conversation
* ci: require verified dev-to-main promotions * fix: pin examples MCP SDK to audited graph (#3) Co-authored-by: sjungwon03 <> * fix(deps): adopt TypeMCP 0.2.2 remediation (#7) * chore: reconcile main release history into dev (#11) * release: publish verified TypeChain and TypeMCP examples (#1) Co-authored-by: sjungwon03 <> * release: promote audited MCP SDK graph to production (#5) * ci: require verified dev-to-main promotions * fix: pin examples MCP SDK to audited graph (#3) Co-authored-by: sjungwon03 <> --------- Co-authored-by: sjungwon03 <> * fix: retain published TypeMCP dependency contract * fix: remove obsolete reconciliation override --------- Co-authored-by: sjungwon03 <>
sjungwon03-ai
approved these changes
Jul 29, 2026
sjungwon03-ai
left a comment
sjungwon03-ai
left a comment
Member
There was a problem hiding this comment.
Formal independent review at exact HEAD 4cff958. Verified: true two-parent merge (parents 69f9ee8 dev + 3d07fa8 main); zero file changes from dev — no Swagger Petstore or dependency-graph mutation; current main becomes a direct ancestor after merge, enabling the dev-to-main release-promotion flow; exact-head verify check green (run 30415932215, head_sha-bound); zero open review threads. This is a history reconciliation with no product or dependency delta. APPROVE.
This was referenced Jul 29, 2026
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
2 participants
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.
Summary
Closes #17.
Create an ancestry-preserving reconciliation before the Swagger Petstore release promotion:
devparent:69f9ee84376fba11c42f7e16755c71804fb1e564(reviewed Petstore feature merge)mainparent:3d07fa84dd671c8136719756274aab320d87570f4cff958ede3e26236c2491e5de5132cd6e9f0f0eThe merge has no content delta from
dev; it retains the reviewed Petstore implementation and restoresmainas a real ancestor ofdev. This is required because the release-promotion workflow acceptsdevas the only promotion source.Verification
devand nooverridesreintroduction.npm cinpm run check— 8 test files / 12 tests and production audit reports 0 vulnerabilities.npm run example:petstore:typemcp:fixturenpm run example:petstore:agent:fixturegit diff --check origin/dev...HEADScope
No Petstore API, TypeMCP tool, TypeChain workflow, dependency, or documentation behavior changes.