"last n versions" includes unstable ones
See original GitHub issueOne could expect that e.g. specifying “last 3 Chrome versions” will be reasonably safe as that’s what’s promoted in README. However, that’s not the case:
$ browserslist "last 3 Chrome versions"
chrome 59
chrome 58
chrome 57
This includes ONLY unstable versions of Chrome. That’s not good.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:17 (12 by maintainers)
Top Results From Across the Web
1.6. Lifecycle of a Release
The project will simultaneously have three to six different versions of each program, named Experimental, Unstable, Testing, Stable, Oldstable, and even ...
Read more >n - npm
Interactively Manage All Your Node Versions. Latest version: 9.0.1, last published: 2 months ago. Start using n in your project by running ...
Read more >apt_preferences(5) — apt - unstable - Debian Manpages
list(5) file contains references to more than one distribution (for example, stable and testing). APT assigns a priority to each version that is ......
Read more >How can the default node version be set using NVM?
1. Addition: alias works as long as you're not installing new versions. · 101. Use nvm alias default node to make the "latest"...
Read more >Shopify API versioning
There is always an unstable version of the APIs available. The unstable versions contain features and changes that are still in progress, and...
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
Done. 6.7.1 was released.
@ben-eb fix — first 3 versions is “unreleased”