Select only last minors for multiple major versions?
See original GitHub issueFirst: Thanks for creating this! 😃
Is it currently possible to select only the last minor versions for multiple major versions using a relative query?
Example: For safari
only 11.1 and 10.1.
If not, it would be nice to be able to, e.g. as browserslist "last 2 safari major-minor versions"
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Minor versions, major problems - Ellen's Digital Workplace
Users have to choose between major or minor version, and I have experienced that not everyone knows the difference. (I once noticed a...
Read more >Major vs. Minor Versions in SharePoint Online
How do you decide between Major vs. Minor Versions in SharePoint Online? I explain in great detail in this article.
Read more >Semantic Versioning 2.0.0 | Semantic Versioning
Precedence for two pre-release versions with the same major, minor, and patch version MUST be determined by comparing each dot separated identifier from...
Read more >versioning - Document Library-Major and Minor Views
What I am trying to do is have it so that there is a view which shows only the major versions of the...
Read more >Using only major versions in url doesn't fully work. #852 - GitHub
This seems to be working as long as I specify a controller with [ApiVersion(1.0)] , but as soon as I specify a minor...
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
It’s the support I have to work with: “last 2 versions of safari, always the latest minor”.
I’d argue it does make some sense, because why support something at lower minor level (like
ios_saf 10.0-10.2
) if the vendor itself has released a higher minor version, which is available for everyone with the major version (e.g.10.3
). One example for a feature is https://caniuse.com/#feat=css-grid: Supported since 10.3.For now we went with
ios_saf >= 10.3
, which of course is absolute but might point to a more acceptable feature request: A relative query to select every version since the last minor version of a major version.Maybe like
last 2 ios_saf major versions last minor
⇒Of course there currently is
last 3 ios_saf versions
which leads to the output above, but we hesitated to use it, because its not as explicit. If for example 11.4 will get its own entry (and not become 11.3-11.4), that query would unintentionally drop 10.x.I do think this is a specific request and might not justify the effort or added complexity and thus understand if you closed it. Apologies if something is unclear.
I think this really comes down to Safari not using semver since they only release one major release per OS version, but can release several significant updates during the life of the OS and make a minor version bump for major updates. If they used semver correctly like any other developer this wouldn’t be an issue.
More examples include
Object.values()
, CSS grids, andfetch()
being introduced in 10.1, and everything from CSS font rendering improvements to service workers in 11.1. You can clearly see how their minver is actually a major version jump by viewing the waterfall at the bottom of the page on caniuse.com.I’m not sure what the rule would look like, but we tell our macOS and iOS users that we support the latest version of Safari in the last two major macOS and iOS versions.