You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The GitHub Actions workflow is generating a deprecation warning due to the use of Node.js 16. GitHub Actions now requires the use of Node.js 20, as Node.js 16 actions have been deprecated.
To Reproduce
Steps to reproduce the behavior:
Go to the GitHub repository containing the workflow.
Run the GitHub Actions workflow.
Observe the deprecation warning in the workflow logs.
The warning specifically mentions the use of Node.js 16 in aws-actions/amazon-ecr-login@v1.
Expected behavior
The expected behavior is for the GitHub Actions workflow to run without any deprecation warnings. It should use the updated Node.js 20 environment for all actions.
Screenshots
Desktop (please complete the following information):
OS Agnostic
Additional context
The deprecation of Node.js 16 actions is part of GitHub's ongoing maintenance and update of their Actions infrastructure. More information about this transition can be found at: GitHub Blog Changelog.
The text was updated successfully, but these errors were encountered:
Describe the bug
The GitHub Actions workflow is generating a deprecation warning due to the use of Node.js 16. GitHub Actions now requires the use of Node.js 20, as Node.js 16 actions have been deprecated.
To Reproduce
Steps to reproduce the behavior:
aws-actions/amazon-ecr-login@v1
.Expected behavior
The expected behavior is for the GitHub Actions workflow to run without any deprecation warnings. It should use the updated Node.js 20 environment for all actions.
Screenshots
Desktop (please complete the following information):
OS Agnostic
Additional context
The deprecation of Node.js 16 actions is part of GitHub's ongoing maintenance and update of their Actions infrastructure. More information about this transition can be found at: GitHub Blog Changelog.
The text was updated successfully, but these errors were encountered: