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

Error because of deprecated version of actions/upload-artifact: v3 #141

Closed
ivorbosloper opened this issue Jan 9, 2025 · 11 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@ivorbosloper
Copy link

My github action failed with the following error:

Error: This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3`.
Learn more: https://github.blog/changelog/20

[24](https://github.com/some_repo/actions/runs/1234/job/4567?pr=1#step:1:28)-04-16-deprecation-notice-v3-of-the-artifact-actions/

I have a list of actions I'm using, and the error doesn't state a clear source of the error, but this repository seems to be the only one pointing towards upload-artifact v3, at https://github.com/awalsh128/cache-apt-pkgs-action/blob/master/action.yml#L88

Getting action download info
Download action repository 'actions/checkout@v4' (SHA:11bd71901bbe5b1630ceea73d27597364c9af683)
Download action repository 'awalsh128/cache-apt-pkgs-action@latest' (SHA:a6c3917cc929dd0345bfb2d3feaf9101823370ad)
Download action repository 'actions/setup-python@v4' (SHA:65d7f2d534ac1bc67fcd62888c5f4f3d2cb2b236)
Download action repository 'nyurik/action-setup-postgis@v1' (SHA:b10c6d8544c44e56c00b46174b0b580699a86620)
Download action repository 'MishaKav/pytest-coverage-comment@main' 
@jbergler
Copy link

jbergler commented Jan 9, 2025

Looks like someone has proposed a fix in #140

@suever
Copy link

suever commented Jan 9, 2025

Is GitHub rolling out these failures gradually? The announcement states that they will cause an error starting on January 30th but we're seeing this error now as well (somewhat sporadically)

@frank-west-iii
Copy link

I have a list of actions I'm using, and the error doesn't state a clear source of the error

I was asking around, but does anyone know how to get a dependency tree for GH actions that led you here? I had to hunt and peck all my actions and their dependencies to get here.

JamesWrigley added a commit to European-XFEL/DAMNIT that referenced this issue Jan 9, 2025
Needed because older versions were using a soon-to-be-deprecated action: awalsh128/cache-apt-pkgs-action#141
@awalsh128
Copy link
Owner

PR has been merged and new package published as https://github.com/awalsh128/cache-apt-pkgs-action/releases/tag/v1.4.3

Still need to update the v1 and latest tags; will do tonight PT time. In the meantime, switch to the explicit version.

@awalsh128 awalsh128 added the bug Something isn't working label Jan 9, 2025
@awalsh128
Copy link
Owner

Is GitHub rolling out these failures gradually? The announcement states that they will cause an error starting on January 30th but we're seeing this error now as well (somewhat sporadically)

There is another notice that points out brownouts for the package for 2025-01-09.

https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/

Although being a dependency we get a blackout. :(

@ivorbosloper
Copy link
Author

This has been fixed, thanks

takluyver pushed a commit to European-XFEL/DAMNIT that referenced this issue Jan 10, 2025
Needed because older versions were using a soon-to-be-deprecated action: awalsh128/cache-apt-pkgs-action#141
@awalsh128
Copy link
Owner

Thanks for confirming. Will close once alias tags are updated.

@FezVrasta
Copy link

This is happening again to us with latest 🤷‍♂️

@GoodbyeNJN
Copy link

Same here.

I noticed in my action log, downloaded tarball SHA is a6c3917cc929dd0345bfb2d3feaf9101823370ad with awalsh128/cache-apt-pkgs-action@latest or awalsh128/cache-apt-pkgs-action@v1, which does not point to the latest commit. This is very strange. I am not sure if it is a problem with Github itself.

@maximeantoine1997
Copy link

We had the same issue. We explicitly set the version to v1.4.3 and it worked again.

@awalsh128
Copy link
Owner

#145 is already an open issue to update the tags. Hoping to get it done tonight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants