ci: add RC publishing to the release workflow - #452
Open
danstepanov wants to merge 2 commits into
Open
Conversation
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.
Adds RC publishing to the existing release workflow. Each candidate uses an exact version and a reviewed archive checksum. The action verifies npm authentication, publishes the archive under rc-staging, checks the registry package and a clean Expo installation, then advances rc while preserving latest.
Includes a preflight mode, bounded registry propagation checks, and safe retries after a partial publication. Existing stable and preview releases continue to use release-it.
Tested with 15 publication guard tests and all 42 engine Node tooling tests against a fresh npm installation of 3.1.0-rc.0. The registry archive matches the audited package byte for byte. Workflow parsing and formatting checks pass.