chore(release): reconcile main history for agent promotion - #24
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 * feat: add read-only Swagger Petstore agent examples (#16) * docs(planning): add Swagger Petstore agent plan * feat: add read-only Swagger Petstore client * feat: wrap read-only Petstore API in TypeMCP * feat: add TypeChain Petstore agent workflow * feat: add live Swagger Petstore demonstrations --------- 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.
Independent release-history reconciliation review at exact HEAD a0bf940.
Verified:
- Two-parent merge: first parent 76d4171 (dev), second parent a74b30a (main) — confirmed via commit API.
- Zero file delta against dev (0 changed files, +0/-0) — pure history reconciliation, no product change.
- Dev content preserved: real agent factory (typechain-petstore-real-agent.ts), fixture script, test (typechain-petstore-real-agent.test.ts), docs/planning intact; no
overridesin package.json; TypeMCP pinned at ^0.2.2. - Exact-head CI green: run 30417614139 conclusion=success on this SHA. Zero review threads, zero inline comments.
Approving for merge into dev to unblock real TypeChain Petstore agent promotion to main.
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 #23.
Create the ancestry-preserving release-history reconciliation required before promoting the real TypeChain Petstore agent to
main.a0bf940545f025b4b985191904dc49b6a852e561dev:76d4171ab111ab69c77924ab90b4cb829f83701amain:a74b30a0e8aab7173adcca2a8b38fb5064811d31The merge preserves current
devas the resolution for the two historical README/package conflicts. It introduces no product behavior, TypeMCP tool, TypeChain agent, dependency, lockfile, or workflow change fromdev, while makingmaina direct ancestor after the reconciliation merges.Verification
overridesis present and TypeMCP remains^0.2.2.npm cinpm run check— 9 test files / 13 tests and audit 0 vulnerabilities.npm run example:petstore:agent:real:fixturegit diff --check origin/dev...HEAD