Log Node.js version using about setup-node

[joshmgross]

👋 Hey @fishcharlie. Specifying a node-version of 10 and 10.x will have the same result. This follows semver, where 10 == 10.x == 10.x.x, which is effectively "the latest version of Node.js v10 taking into account both minor and patch versions.

Finally, it'd be great if this action printed the Node.js version it decided to use in the logs of GitHub Actions

Great idea! That should be a quick fix.

[joshmgross]

@bryanmacfarlane are you still planning on doing this? If not, I can pick this up.

[bryanmacfarlane]

@joshmgross - I'm fine with you picking this up. If you do, look at recent commits in setup-go where I did it. I think it should also output npm version.

[fishcharlie]

@joshmgross Would be more than happy to review and/or test a PR for this when you have it up! Thanks so much for helping with this.

[bryanmacfarlane]

Yes, it should work with any semver version spec. As part of this issue, I'll make sure it's logged as well. I'll also update the readme / docs

[fishcharlie]

Any updates on this? cc/ @bryanmacfarlane @joshmgross

[fishcharlie]

Outputting the npm version too would be amazing!!!

[demian85]

Can someone please explain why my node version is not 12 as specified?

Part of my config file is

jobs:
  primary:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [12.x]

    steps:
      - uses: actions/checkout@v1

      - name: Cache node modules
        uses: actions/[email protected]
        with:
          path: ~/.npm
          key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
          restore-keys: |
            ${{ runner.os }}-node-
      - name: Node ${{ matrix.node-version }}
        uses: actions/[email protected]
        with:
          node-version: ${{ matrix.node-version }}

      - name: Installing dependencies
        run: npm install

And logging the node version to the console results in node version: 10.20.1

I do not quite understand where is the problem.

[bryanmacfarlane]

@demian85 can you log a separate issue? I would also try setup-node@v1 to ensure you're getting latest along with bug fixes

Here's a workflow of mind doing @ 12.x and it leads to node 12. https://github.com/bryanmacfarlane/actions-playground/runs/570652210?check_suite_focus=true

[joshmgross]

PR for this here: #137

[EdJoPaTo]

This was resolved via #137 but its not working anymore?

Log from the used action isnt showing the specific NPM version:

Run actions/setup-node@v2
  with:
    node-version: 16
    always-auth: false
    check-latest: false
    token: ***
Attempting to download 16...
Acquiring 16.11.1 - x64 from https://github.com/actions/node-versions/releases/download/16.11.1-1336322549/node-16.11.1-linux-x64.tar.gz
Extracting ...
/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword -C /home/runner/work/_temp/192ce410-4dad-49a1-99ac-d942052f626f -f /home/runner/work/_temp/5a93bf66-8337-45eb-b047-0b5bb8eab63e
Adding to the cache ...
Done

Run actions/setup-node@v2
  with:
    node-version: 14
    always-auth: false
    check-latest: false
    token: ***
Found in cache @ /opt/hostedtoolcache/node/14.18.0/x64

[joshmgross]

Looks like the changes added in #137 were inadvertently removed in #147

[dmitry-shibanov]

Hello everyone. We've released a new version 3.5.1 with logging Nodejs version. For now we didn't update the major tag. Could you please confirm that everything works as expected ?

[dmitry-shibanov]

Hello everyone. For now I'm going to close the issue. If you have any concerns feel free to pings us.