[SRE-2781] Set publishing workflows to use prod env #2481
+4
−2
Conversation
This file contains 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
|
View your CI Pipeline Execution ↗ for commit 1eb4593.
☁️ Nx Cloud last updated this comment at |
immutable-art
approved these changes
Dec 20, 2024
|
Relates to #2480 |
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.
TS_IMMUTABLE_SDK_NPM_TOKEN secret will now be stored as an environment secret in prod environment, meaning it will only be accessible from workflows running against prod env. This is to ensure only protected main brain with required reviews is able to publish to NPM to mitigate potential security incidents.
Prod env will require reviewers from the sdk team, and these workflows will only be executable against main.