Closed sarahethompson closed 1 year ago
Workflow Name: Lock Threads Branch: main Run URL: https://github.com/hashicorp/vagrant/actions/runs/4964539933
save-state deprecation warnings: 0 set-output deprecation warnings: 0 node12 deprecation warnings: 1
Please review these deprecation warnings as soon as possible and merge in the necessary updates.
GitHub will be removing support for these commands and plan to fully disable them on 31st May 2023. At this time, any workflow that still utilizes these commands will fail. See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/.
GitHub have not finalized a date for deprecating node12 yet but have indicated that this will be summer 2023. So it is advised to switch to node16 asap. See https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
If you need any help, please reach out to us in #team-rel-eng.
There's a proposed PR in https://github.com/hashicorp/vagrant/pull/13175
Workflow Name: Lock Threads Branch: main Run URL: https://github.com/hashicorp/vagrant/actions/runs/4964539933
save-state deprecation warnings: 0 set-output deprecation warnings: 0 node12 deprecation warnings: 1
Please review these deprecation warnings as soon as possible and merge in the necessary updates.
GitHub will be removing support for these commands and plan to fully disable them on 31st May 2023. At this time, any workflow that still utilizes these commands will fail. See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/.
GitHub have not finalized a date for deprecating node12 yet but have indicated that this will be summer 2023. So it is advised to switch to node16 asap. See https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
If you need any help, please reach out to us in #team-rel-eng.