continuous integration - How to use a specific version of GitHub actions? Specifically actionsupload-artifact@v3 with node20 sup

In my GitHub actions flow, I am using actions/upload-artifact@v3. Lately I've been getting the following warning:

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/upload-artifact@v3. For more info: /changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

This issue was being tracked here, with the solution to upgrade to upload-artifact@v4. The problem is that v4 is not available on GitHub Enterprise Server (GHES).

I found that upload-artifact cut a release for node 20 and there is a v3-node20 tag, which tells me they have made support for v3 + node20. My question is: how can I use this release? Trying actions/upload-artifact@v3-node20 and actions/[email protected] both throw errors:

Unable to resolve action actions/upload-artifact@v3-node20, unable to find version v3-node20

In my GitHub actions flow, I am using actions/upload-artifact@v3. Lately I've been getting the following warning:

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

This issue was being tracked here, with the solution to upgrade to upload-artifact@v4. The problem is that v4 is not available on GitHub Enterprise Server (GHES).

I found that upload-artifact cut a release for node 20 and there is a v3-node20 tag, which tells me they have made support for v3 + node20. My question is: how can I use this release? Trying actions/upload-artifact@v3-node20 and actions/[email protected] both throw errors:

Unable to resolve action actions/upload-artifact@v3-node20, unable to find version v3-node20

• github
• continuous-integration
• github-actions

Share Improve this question Follow edited Feb 4 at 1:29 hakre 198k5555 gold badges450450 silver badges856856 bronze badges asked Feb 3 at 23:27 KronKron 1931010 bronze badges 1

• Migration to v4 has been taken from GHES roadmap until a better planning can be made. See #537 – hakre Commented Feb 4 at 2:33

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

It should work with @

According to the following examples:

• https://github.com/ankhorg/NeigeItems-Kotlin/actions/runs/11477637242/workflow#L71
• GitHub Actions [email protected] Path Patterns Not Working After Upgrade

We can refer a git tag as version version with the syntax you shared:

actions/acme-reository@tag

Suggestion: Try with actions/[email protected] and share us the result

branches vs tag

Usually using @xyz you can access directly to the branch or tag.

The branch you are trying to use is special because it has "/" in the branch name: v3/node20. Maybe this is the error

Suggestion: Try with

actions/upload-artifact@v3/node20

Try with other actions

If the previous approaches doesn't work, it could be:

• A problem with your yaml file
• The version you are looking for is forbidden or deleted

To validate if it is an error related only to specific versions of actions/upload-artifact or GHES:

• Use another action with @tag or @branch
• Use the same actions/upload-artifact but with a recent branch or tag.