Repository navigation
Automatically deliver public product releases through Pages - #40
Merged
Merged
Conversation
showxu
enabled auto-merge (squash)
October 6, 2026 05:27
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
1 participant
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.
Pages now imports the latest verified public Computer MCP release before deployment. Its existing automation App creates a signed, single-file release-record proposal and merges it only after required website CI; the subsequent build uses current canonical master.
The importer supports latest stable discovery while retaining digest/tag verification and version nonregression. The publisher rejects unrelated changes, unsigned proposals and source races, preserves the caller index, and leaves the deployed site intact on failure. Synchronization runs on the existing hourly schedule, master pushes and manual dispatch.
Cloud validation covers website checks and proposal ownership/immutability regressions. No local metadata import or cross-repository credential is required for each release.