Repository navigation
Conversation
This branch has not been deployed
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.
Prepares HIG 0.1.0 for npm publication from the self-hosted Mac minis. Nothing is published, tagged or released by this PR.
publish.yml
[self-hosted, macOS, ARM64]. No GitHub-hosted runners.v*tag, or byworkflow_dispatchwith a requiredtaginput. Checks outrefs/tags/<tag>.NPM_TOKENsecret (NODE_AUTH_TOKENvia setup-noderegistry-url). Removes OIDC (id-token: write),--provenance, thenpm-releaseenvironment and the reviewer/quality-run prerequisites job. The job re-runs every gate on the tag commit itself.check→quality→release:dry-run --channel stable-simulation→verify-release.mjs→ publish →smoke:registry. Publishes in dependency order and skips versions that are already published, so an interrupted run can be resumed. The registry hash check still catches byte mismatches.actions/cacheand no setup-nodecache:. Fonts are generated fresh withscripts/ci-generate-fonts.sh. No globalnpm installon the shared minis.playwright install chromiumwithout--with-deps.Other changes
scripts/registry-smoke.mjs: drops the npm provenance-attestation assertions, because token publishing has no attestations. Keeps the tarball SHA-256 equality and consumer smokes.tests/ci-runners.test.ts: now also coverspublish.yml(self-hosted macOS only, no apt/sudo/--with-deps).docs/governance/release.md,docs/ci-runners.md, plus regenerated docs output) updated to describe the new mechanism.planning/release-blockers.json: updates the wording of thetask-policyreason only. No blocker status changed.CHANGELOG.mdwith the 0.1.0 entry.Versions
The root package and all eight packages (
@bloxwap/hig-chart,-contracts,-feedback,-native,-native-fonts,-og-fonts,-react,-tokens) and their internal ranges were already0.1.0on main. No bump was needed.Local validation (Linux box)
npm ci, font generation,npm run check(172 web + 169 native tests),npm run quality,release:dry-run --channel stable-simulation(8 artifacts) and actionlint all pass.verify-releasefails as expected withRelease gates remain: task-policy, source-audit, native-fonts, physical-devices, owning-migrations, upstream-feedback-gaps. Publishing needs those gates cleared, or approved as exceptions by the owner, first.