Improve documention on version input (semver spec behavior in readme)
See original GitHub issueHi,
As far as I see, there’s no way to use the latest node version without manually specifying it.
I want to be able to run my tests in the latest node version without updating it each time a new version came out.
It could be achieved with the keyword 'latest'
or 'node'
in the same way you can do with NVM
.
Cheers
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Semantic Versioning 2.0.0 | Semantic Versioning
Semantic Versioning 2.0.0. Summary. Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes ...
Read more >vscode-node-readme - Visual Studio Marketplace
A vscode extension to view javascript module documentation in editor. ... Launch VS Code Quick Open ( Ctrl+P ), paste the following command,...
Read more >Conventional Commits
The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an...
Read more >Configuration — python-semantic-release 7.32.2 documentation
README.rst:VERSION (\d+\.\d+\.\d+) ... So the above example would probably be better written as: ... Quote from Semantic Versioning Specification:.
Read more >package.json - npm Docs
A lot of the behavior described in this document is affected by the ... Version must be parseable by node-semver, which is bundled...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@GMartigny - thanks, I’ll re-open and morph to a doc issue. One small note - it’s not a workaround 😉 the semver spec is a feature and the way we believe it should work. I’ll update the readme.
Hello @GMartigny. The
latest
input can install nonlts
version, which is now 17, and thelts/*
input will download thelts
version, which is now 16.