Repository navigation
Publish through GitHub environments so releases show as deployments - #14
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
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.
The npm, GitHub Packages and Homebrew jobs of the Release workflow now run in environments of those names, each with a link to what it published. The repo sidebar gets a Deployments section showing which version each channel has and when it shipped.
The three environments already exist and only accept the
mainbranch.Before the next release: npm's trusted publisher has to name the
npmenvironment, because the OIDC token now carries it. That setting is on npmjs.com (package settings, Trusted Publisher, Environment name:npm).