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

Yarn installs failing in GitHub Actions after updating to Node 23.0.0 #1157

Open
2 of 5 tasks
danascheider opened this issue Nov 6, 2024 · 2 comments
Open
2 of 5 tasks
Assignees
Labels
bug Something isn't working

Comments

@danascheider
Copy link

Description:
I have a React app that uses GitHub Actions for CI. After upgrading its Node version to 23.0.0, the dependency installation step fails saying "The remote archive doesn't match the expected checksum." I am not able to replicate these errors in my local environment.

This is set up in my .github/workflows/ci.yml file as follows:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4
      with: fetch-depth: 0
    - uses: actions/setup-node@v4
      with:
        node-version: "23.0.0"
    - name: "install Node Modules"
      run: yarn

As soon as I changed node-version: "22.11.0" to node-version: "23.0.0", the builds started failing.

Action version:
v4

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
Node: 23.0.0
npm: 10.9.0
yarn: 3.6.4

Repro steps:
This is an example of one of the failing builds. I made two PRs that failed. The commonalities are that Node is updated to 23.0.0 in the package.json, .tool-versions, and ci.yml files.

Expected behavior:
I expected my build to continue running, and passing, like it was until I updated Node.

Actual behavior:
yarn install fails, indicating that "The remote archive does not match the expected checksum"

@danascheider danascheider added bug Something isn't working needs triage labels Nov 6, 2024
@mahabaleshwars
Copy link

Hello @danascheider,
Thank you for creating this issue. We will investigate it and provide feedback as soon as we have some updates.

@priyagupta108
Copy link
Contributor

Hi @danascheider 👋,
It appears there's an issue on Node's side with version 23.0.0. For more details, see nodejs/node#55414
To resolve this, use the latest version of Node 23, which is 23.2.0. Alternatively, you can specify:

uses: actions/setup-node@v4
with:
  node-version: '23'

This configuration ensures that the action will automatically download the latest available release for Node.js version 23.

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

3 participants