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
set-env disabled for Github Actions #535
Comments
Thanks, @kamronbatman. In fact the symptom you describe that nbgv builds are failing is not due to this code location. That symptom is already fixed in #516. If you're still seeing this in your github workflow, make sure you're using the latest version of Nerdbank.GitVersioning and/or the As this repo does not build on GitHub Actions, the code location you call out is not actually impacting anything. It's merely there because this script is shared across many repos. The master location of this script was updated recently so this repo will get an update eventually when I copy over the latest script. |
Not sure why then but I am having that issue with the newest github actions version. It stopped erroring when I turned off setting the variables in version.json. hmm |
@kamronbatman The |
EDIT: Thanks! |
Github has disabled
set-env
:Nerdbank.GitVersioning/azure-pipelines/Set-EnvVars.ps1
Line 49 in 57a4826
So builds that use NBGV for versioning are failing.
More info:
GHSA-mfwh-5m23-j46w
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
The text was updated successfully, but these errors were encountered: