We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
GitHub Actions is deprecating set-env and add-path commands as outlined by
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Therefore starting from version 2.273.5 of the runner GenerateBuildLogOutput outputs
GenerateBuildLogOutput
Environment files should be used instead
https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-commands-for-github-actions#environment-files
Use env files to not trigger the warning
See PR
Run a build with GitVersion using GitHub actions
The text was updated successfully, but these errors were encountered:
🎉 This issue has been resolved in version 5.5.0 🎉 The release is available on:
Your GitReleaseManager bot 📦🚀
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
GitHub Actions is deprecating set-env and add-path commands as outlined by
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Therefore starting from version 2.273.5 of the runner
GenerateBuildLogOutput
outputsEnvironment files should be used instead
https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-commands-for-github-actions#environment-files
Expected Behavior
Use env files to not trigger the warning
Actual Behavior
Possible Fix
See PR
Steps to Reproduce
Run a build with GitVersion using GitHub actions
Context
Your Environment
The text was updated successfully, but these errors were encountered: