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
Does not support configured Node.js version #96
Comments
The issue may originate from here: semantic-release-action/action.yml Line 47 in e878537
This must not be hard-coded. Overall, version 12 is archaic at this time and it'd be great for this action to use LTS for better stability and not to block other tools that wish to migrate to the recent version of Node.js. |
I am willing to open a pull request if you can guide me through the approach you find suitable here. I'd either set |
Thanks for your suggestion. I will switch to 'node16' soon after checking the compatibility. |
I switch to |
Thank you for your swift action on this, @cycjimmy! 🎉 |
Describe the bug
A clear and concise description of what the bug is.
Semantic release action disregards the Node.js version previously configured in the same job.
Workflow
Expected behavior
Semantic release must execute itself and any sub-commands using the globally available Node.js version (in the case above
16.14.0
, not12.13.1
).Additional context
Looks like it fallbacks to some default Node.js version but I see no options to disable this fallback.
The text was updated successfully, but these errors were encountered: