Repository navigation
Add environment protection to release workflow - #127
Merged
Merged
Conversation
- Require approval from 'production' environment before publishing - Applies to both VS Code and IntelliJ release jobs - Prevents unauthorized releases to marketplaces
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
Adds environment protection to the release workflow to prevent unauthorized releases to VS Code and JetBrains marketplaces.
Changes
environment: productionto bothrelease-vscodeandrelease-intellijjobsHow It Works
Setup Required
After merging, you'll need to configure the "production" environment in GitHub:
productionrelease/*patternSecurity Benefit
Prevents accidental or unauthorized releases by requiring explicit approval from trusted maintainers before publishing to marketplaces.