Repository navigation
fix(release): separate registry environments - #30
Merged
Merged
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.
Summary
Release publications need separate GitHub environments after the npm environment was renamed. Route npm staging through
npmjsand GitHub Packages publication through the newly createdgithub-packagesenvironment, with each deployment linking to its registry package page. Run finish_release only when a GitHub release is published, removing the manual trigger and its inputs. Preserve independent matrix jobs, failed-job retries, staged npm publication, and existing PR/edge workflows; update the release guidance.Validation
git diff --checkpassed. Only actionlint's outdatedubuntu-26.04runner-label check was excluded.npmjsandgithub-packagesexist and supplied the GitHub package page URL.