Skip to content
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

[Bug] GenerateBuildLogOutput for Github actions uses deprecated set-env command #2421

Closed
danielmarbach opened this issue Oct 9, 2020 · 1 comment · Fixed by #2422
Closed
Labels
Milestone

Comments

@danielmarbach
Copy link
Contributor

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

image

Environment 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

image

Possible Fix

See PR

Steps to Reproduce

Run a build with GitVersion using GitHub actions

Context

Your Environment

  • Version Used:
  • Operating System and version (Windows 10, Ubuntu 18.04):
  • Link to your project:
  • Link to your CI build (if appropriate):
@arturcic
Copy link
Member

🎉 This issue has been resolved in version 5.5.0 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants