Add non-publishing release preflight and gate all destinations - #4
Open
foundev wants to merge 1 commit into
Open
Add non-publishing release preflight and gate all destinations#4foundev wants to merge 1 commit into
foundev wants to merge 1 commit into
Conversation
foundev
had a problem deploying
to
packages-publish
September 10, 2026 15:23 — with 
GitHub Actions
Failure
GitHub Actions
Failure
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.
Release validation currently needs an already-published GitHub release and finalizes it before npm validation. Allow a proposed-version
publish=falsedispatch at a preparation commit, build native and npm deliverables in one workflow, and check all versions plus the actual publishing job credentials before any final upload. Finalize GitHub only after all npm packages verify, and preserve conflicts during partial recovery.Add independent exact-commit checks, payload-aware archive verification, and document all seven destinations and their credentials. npm authorization deliberately fails if direct publishing trust cannot be inspected; an OIDC exchange alone can also authorize staging-only publication.
Validation: 28 Python tests passed locally, including wrong-SHA/failed-run rejection, conflicting tags, permission failure before uploads, compression differences, and read-only recovery. Exact-commit GitHub CI and non-publishing preflight will be inspected before completion. No release tags, public releases, final assets, or registry packages are published by this PR or its branch pushes.