- Notifications
You must be signed in to change notification settings - Fork261
fix(cmd-version): prevent errors when PSR is executed in non-GitHub CI environments#1322
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
codejedi365 merged 1 commit intopython-semantic-release:masterfromcodejedi365:fix/github-actions-output-non-github-errorSep 6, 2025
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
…I environmentsNOTICE: Unfortunately, PSR introduced a bug in 10.3.0 when attempting to provide more CIoutputs for GitHub Actions. It required our GitHub client interface to be loaded andeven if it was not using GitHub CI to be run. This caused errors in Gitea and likelyGitLab/Bitbucket environments. This change prevents that from happening but if anyusers pipelines were intentionally presenting the environment variable "GITHUB_OUTPUT"to enable action output to enable passing along internal outputs of PSR then theirhack will no longer work after this change.Resolves:python-semantic-release#1315
4df4be4 intopython-semantic-release:master 9 checks passed
Uh oh!
There was an error while loading.Please reload this page.
🎉 This PR has been published as part of v10.3.2 🎉You can find more information about this release on theGitHub Releases page. |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
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.
Purpose
Rationale
Unfortunately, PSR introduced a bug in 10.3.0 when attempting to provide more CI outputs for GitHub Actions. It required our GitHub client interface to be loaded and even if it was not using GitHub CI to be run. This caused errors in Gitea and likely GitLab/Bitbucket environments. This change prevents that from happening but if any users pipelines were intentionally presenting the environment variable "GITHUB_OUTPUT" to enable action output to enable passing along internal outputs of PSR then their hack will no longer work after this change.
PR Completion Checklist
Reviewed & followed theContributor Guidelines
Changes Implemented & Validation pipeline succeeds
Commits follow theConventional Commits standard
and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)
N/A
Appropriate Unit tests added/updatedN/A
Appropriate End-to-End tests added/updatedN/A
Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)