Unable to find actions actions/setup-node@v2

[antek-drzewiecki]

I was trying to upgrade from actions/setup-node@v1 to actions/setup-node@v2.

Following the documentation from the action page i've replaced v1 with v2.
Upon running the action we get the following message.

.github#L1

Unable to resolve action `actions/setup-node@v2`, unable to find version `v2`

Is it something with the documentation? Is v2 still in beta? Or which tags should we use?

[stefankip]

Yeah same problem here. I now use setup-node@v2.1.2 which works, but would like to use v2 instead.

[Roriz]

https://github.com/actions/setup-node/blob/main/README.md#v2-beta

[JamesIves]

Generally speaking you probably shouldn't point to a release branch of an action. Use a specific version found on the marketplace, otherwise you'll run the risk of breaking changes affecting your production workflows.

[stefankip]

Well I assume no breaking changes will be introduced within a single major version to be honest...

[JamesIves]

Well I assume no breaking changes will be introduced within a single major version to be honest...

I wouldn't assume that as you're referencing a branch directly and not a tagged version. Use a tagged version with Dependabot to keep your workflows up to date. If the maintainer forgets to commit something, or is mid-deployment, your workflow could potentially break.

[maxim-lobanov]

Hello everyone!
We have recently released stable actions/setup-node@v2 that points to v2.1.4 that is marked as stable too. Also updated README properly.
I am closing this issue but please let me know if you have any concerns.

[pierregangloff]

This is still an issue for me but maybe it's because we use GitHub Enterprise Server 3.0.1 (GHES: hosted in our own servers)? We need to ask whoever installed our GHES to update the installation to pick up the v2 actions, correct? Would you recommend we switch back to the GitHub SAAS? Are customers encouraged to move back to the SAAS? I.e.: are customers like us, who installed GHES starting to transition back to the SAAS GitHub so that they stop having to manage all of that? To me, that sounds like the way to go.

In the meantime (until they update our local version of GHES, if that is the issue), I guess I should use the self-hosted actions, right?

name: Scala CI

on:
  workflow_dispatch:
  push:
    branches:
    - Development
  pull_request:
    branches:
    - Development

jobs:
  build-job:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2
    - uses: actions/setup-java@v2
      with:
        distribution: 'adopt'
        java-version: 8
    - uses: actions/setup-node@v2
      with:
        node-version: '15'

The error is:

Current runner version: '2.273.5'
Runner name: 'ip-xxxxx'
Machine name: 'ip-xxxxx'
Prepare workflow directory
Prepare all required actions
Getting action download info
Failed to resolve action download info. Error: Unable to resolve action `actions/setup-java@v2`, unable to find version `v2`
Unable to resolve action `actions/setup-node@v2`, unable to find version `v2`
Retrying in 18.311 seconds
Failed to resolve action download info. Error: Unable to resolve action `actions/setup-java@v2`, unable to find version `v2`
Unable to resolve action `actions/setup-node@v2`, unable to find version `v2`
Retrying in 10.931 seconds
Error: Unable to resolve action `actions/setup-java@v2`, unable to find version `v2`
Unable to resolve action `actions/setup-node@v2`, unable to find version `v2`

Thanks!!

[Fitmavincent]

I don't mean to dig grave here, but this issue doesn't seem to be resolved.

on:

  push: 
    branches: [ master ]
  pull_request: 
    branches: [ master ]

  workflow_dispatch:

jobs:
  build: 
    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [14.x]

    steps: 
      - name: Checkout crawler-app
        uses: actions/checkout@v2

      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@2
        with: 
          node-version: ${{ matrix.node-version }}

      - name: Install Dependencies
        run: npm ci

      - run: npm run build

      - name: Deploy to Netlify
        uses: nwtgck/actions-netlify@1.2
        with: 
          publish-dir: './dist'
          production-branch: master
          github-token: ${{ secrets.GITHUB_TOKEN }}
          deploy-message: "Deploy from Github actions"
          enable-pull-request-comment: false
          enable-commit-comment: true
          overwrites-pull-request-comment: true
        env:
          NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
          NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}
        timeout-minutes: 1

[dmitry-shibanov]

Hello @Fitmavincent. You specified the wrong version for the setup-node action. It should be uses: actions/setup-node@2 -> uses: actions/setup-node@v2.

[Fitmavincent]

Hello @Fitmavincent. You specified the wrong version for the setup-node action. It should be uses: actions/setup-node@2 -> uses: actions/setup-node@v2.

Thank you very much @dmitry-shibanov.

[crswll]

@dmitry-shibanov This had me stumped for a good ten minutes just now hahaha. Thank you!