-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Log Node.js version using #90
Comments
👋 Hey @fishcharlie. Specifying a
Great idea! That should be a quick fix. |
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 |
Any updates on this? cc/ @bryanmacfarlane @joshmgross |
@bryanmacfarlane are you still planning on doing this? If not, I can pick this up. |
@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. |
Outputting the npm version too would be amazing!!! |
Can someone please explain why my node version is not 12 as specified? Part of my config file is
And logging the node version to the console results in I do not quite understand where is the problem. |
@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 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. |
PR for this here: #137 |
This was resolved via #137 but its not working anymore? Log from the used action isnt showing the specific NPM version:
|
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 ? |
Hello everyone. For now I'm going to close the issue. If you have any concerns feel free to pings us. |
show command - small output changes
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] * [auto] docs: update contributors badge Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
Couple of things.
First if you specify
node-version
of10
, does that use the absoute latest version of Node.js v10 (both minor and patch versions)?Second, does
node-version
of10.x
use the latest version when taking account patch versions? Or does.x
just mean the minor version?Finally, it'd be great if this action printed the Node.js version it decided to use in the logs of GitHub Actions so developers can determine which Node.js version it decided to use, which would make debugging SO much easier.
The text was updated successfully, but these errors were encountered: