search

AArnott / Library.Template

A template for a NuGet package with tests, stylecop, fxcop, versioning, and Azure Pipelines build ready to go.
MIT License
131 stars 26 forks source link

Set-Env and add-path commands are deprecated in GitHub Actions #79

Closed SteveBush closed 3 years ago

SteveBush commented 3 years ago

GitHub due to a vulnerability has moved to using Environment files: $GITHUB_ENV instead of STDOUT.

The set-env command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files.

Environment Files on Github

Similar problem for add-path.

AArnott commented 3 years ago

Thanks. This is very odd because this was tracked by https://github.com/dotnet/Nerdbank.GitVersioning/pull/516 and the fix for it is already in place in this repo. I'll have to dig deeper I guess.

AArnott commented 3 years ago

Oh! This has nothing to do with that NB.GV bug. It's just the scripts in this repo itself that are calling ::set-env

SteveBush commented 3 years ago

Yes. And I think one instance of ::set-path.

Sent from my iPad

On Nov 16, 2020, at 8:43 AM, Andrew Arnott notifications@github.com wrote:



Oh! This has nothing to do with that NB.GV bug. It's just the scripts in this repo itself that are calling ::set-env

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/AArnott/Library.Template/issues/79#issuecomment-728181180, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAVLFOWCGOT7BR4D453BBRDSQFJCFANCNFSM4TWRJTCQ.