release: promote TypeMCP 0.3.0 to main - #137
Merged
Merged
Conversation
The documentation portal mirrors this repository at a pinned commit and is gaining a Korean edition. Source the translations here so both languages stay reviewable in the repository that owns the prose, rather than being authored separately in the website repository. Each file mirrors its English original section for section and keeps code blocks byte-identical, so an example cannot drift between languages. Every file retains the @theorvane/type-mcp@0.2.2 evidence string the portal's sync step checks. Links to an untranslated document resolve to the English original until its translation lands. Closes #128 Co-authored-by: sjungwon03 <ghrd.sesac4@gmail.com>
chore(release): synchronize main before 0.3.0 promotion
sjungwon03-ai
approved these changes
Aug 3, 2026
sjungwon03-ai
left a comment
sjungwon03-ai
left a comment
Member
There was a problem hiding this comment.
Exact-head release review of 420d32c: main ancestry is preserved through the synchronization merge; 0.3.0 package identity is consistent and no tag, GitHub Release, or npm publication exists yet. Current-head verify and release-promotion checks succeeded, with no unresolved threads. The main-push OIDC/provenance publish path is the intended release action. No blocking findings.
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
devintegration head to release-onlymain.@theorvane/type-mcp@0.3.0only through the protected main-push OIDC/provenance workflow.Linked issue
Closes #136
Verification
420d32c….v0.3.0, GitHub Releasev0.3.0, and npm@theorvane/type-mcp@0.3.0do not yet exist.verifyandrelease-promotionchecksRelease boundary
This PR is the production promotion. On merge, the publish workflow will create the npm provenance publication, immutable tag, and GitHub Release; those artifacts will be verified separately after the workflow completes.