Specify release environment for release job#3001
Merged
smallsaucepan merged 1 commit intomasterfrom Jan 28, 2026
Merged
Conversation
rexxars
pushed a commit
to rexxars/turf
that referenced
this pull request
Feb 11, 2026
Merging without checks as only affects the release build action.
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
2 participants
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 @turf/turf 7.3.2 publish correctly did the trusted publish step 🎉 .
This forces releases to use the
releaseGitHub environment for release jobs.releaseenvironment is currently a basic unrestricted environment at the moment. I'd rather have this specified now, rather than going back to add it later on 115 packages. That lets us restrictreleasefurther later without needing to go back through NPM for all 115 packages 😩 .