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
This action uses actions/upload-artifact@v2, which is deprecated.
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "fingerPrint.log", "fingerPrintInfo.json", "package-lock.json.contrast.log".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
From the link above, this action will no longer be usable starting November 30, 2024.
Starting November 30, 2024, GitHub Actions customers will no longer be able to use v3 of actions/upload-artifact or actions/download-artifact. Customers should update workflows to begin using v4 of the artifact actions as soon as possible. While v4 of the artifact actions improves upload and download speeds by up to 98% and includes several new features, there are key differences from previous versions that may require updates to your workflows. Please see the documentation in the project repositories for guidance on how to migrate your workflows.
This will cause workflow failures for anyone leveraging this action.
Breaking Changes
Due to how Artifacts are created in this new version, it is no longer possible to upload to the same named Artifact multiple times. You must either split the uploads into multiple Artifacts with different names, or only upload once. Otherwise you will encounter an error. https://github.com/actions/upload-artifact?tab=readme-ov-file#breaking-changes
The text was updated successfully, but these errors were encountered:
NodeTestBenches/.github/workflows/ci_build.yml
Line 25 in 9973cd4
This action uses
actions/upload-artifact@v2
, which is deprecated.From the link above, this action will no longer be usable starting November 30, 2024.
This will cause workflow failures for anyone leveraging this action.
The text was updated successfully, but these errors were encountered: