-
Notifications
You must be signed in to change notification settings - Fork 260
ci: Remove environments #1981
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
ko3n1g
wants to merge
1
commit into
main
Choose a base branch
from
ko3n1g/ci/remove-environments
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
ci: Remove environments #1981
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Silent
SVC_PYPI_TEST_TOKENfallback ifSVC_PYPI_TOKENis empty.A known limitation of the
&&/||ternary pattern is that the value after&&must not be falsy; otherwise, the||branch is taken incorrectly. In GitHub Actions, falsy values includefalse,0,-0,"",'', andnull— which covers an unset or empty secret.If
SVC_PYPI_TOKENis ever missing or accidentally revoked, the expression on main/release branches silently resolves toSVC_PYPI_TEST_TOKENand the release is published to TestPyPI instead of production PyPI — with no error or warning. Sincedry-runcan befalsein this workflow, this is a real risk.Consider asserting the secret is non-empty in a pre-publish step, or using
fromJSONindexing to avoid the silent fallback:💡 Alternative ternary pattern that avoids the silent fallback
The
fromJSONarray-index approach usestrue→1/false→0coercion, so it unconditionally selects the correct token without the "falsy middle operand" pitfall.🤖 Prompt for AI Agents