ci(governance): protect binary-only HMG public promotion - #3
Merged
Conversation
monkseekee-max
disabled auto-merge
July 11, 2026 19:17
Contributor
Author
|
@HMG-AI/core-maintainers @HMG-AI/security-managers 请基于最新推送 |
monkseekee-max
enabled auto-merge (rebase)
July 16, 2026 11:53
Contributor
Author
|
Binary-only v1.7.7 release candidate is now built and independently verified.
This promotion remains binary-only: no HMG private release, source sync, website, npm, or PyPI publication. Independent required approvals are still needed; please review without bypassing the protected rules. |
xionghaoh
previously approved these changes
Jul 16, 2026
xionghaoh
self-requested a review
July 16, 2026 12:51
xionghaoh
approved these changes
Jul 16, 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
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.
Outcome
Centralizes a protected binary-only HMG to HMG-public promotion path and keeps the organization workflow-security gate in the same governance change.
Binary-only publication contract
Build public release artifacts (no publish)workflow_dispatchrun from protectedHMG/main.hmg-public-<version>-<source_sha>from that exact run.public-release/,public-release-set.json, andpublic-release-verification.json.verify-hmg-public-release-set.pyis rerun from the exact checked-out source SHA.version.json.main; the logical release tag and checked-in Cargo version must match.This path has no dependency on an HMG private Release, an HMG tag-push workflow, npm publication, website synchronization, or source export. It creates no HMG private Release/tag/npm/site side effects.
Target repository boundary
HMG-public/main.sync-export.shand does not change public product source, website, or npm content.release-provenance/v<version>.json, containing secret-free source repository/SHA/run/artifact and 17-asset digest metadata.HMG-public/main, never reviews itself, and is not a bypass actor.Trust boundaries retained
permissions: {}and receives only canonical validated scalars..githubgovernance and publisher policy remain unchanged by promotion.Organization workflow security
The PR also retains the immutable changed-workflow security gate: exact
github.workflow_shapolicy checkout, exact event-head target checkout, pinned Actions, explicit least privilege, safe hosted runners, untrusted-input controls, and direct-main-write rejection.Verification
actionlint -color: passedbash governance/workflow-policy/test.sh: 41/41 passedgit diff --check: passedActivation boundary
This PR changes central reusable policy only. It does not trigger promotion or publication. Callers and HMG-public wrappers must pin the reviewed merged full SHA before the replacement path becomes active. Auto-merge remains disabled pending independent Core and Security review.