Multiple browsers wrongly reported outdated - sync with baseline data

[WebMechanic]

Hi,

the JSON data (data/browsers.json) and the website contains browser versions listed as "current" which are long outdated and setting any to "the last N versions" results in a false positive. Chromium and Mozilla are +10 versions ahead and Apple will soon skip 10 versions going to v26 in one swoop.

I'd suggest to sync the information with https://github.com/web-platform-dx/baseline-browser-mapping on a regular (monthly) basis and take that data to determine the "last N versions" instead of doing a simple user agent match.

[josselex]

Hi. I had a look at the baseline-browser-mapping but I did not really understand it. Which files would you use as a source?

Meanwhile I updated the browser versions

[WebMechanic]

I'd probably pick on of the *_with_supports.json files and transform that into whatever suits your .json structure so you can make the selection of whatever user agent comes across, then include the new baseline stages as a additional filters to complement "current".

"baseline widely" is going to replace the old concepts of "current" or "last 2 versions" as it's better suited to define a feature set instead of just version numbers which never worked for Safari or other browser that use decimal version numbers. The last two versions of Safari (16, 17) have a very different set of features than i.e. the last two version of Firefox (139, 140) or Chrome/Edge/Opera/Brave.... For Safari, these two numbers represent 10 very different browsers. The equivalent would be selecting Firefox 130 - 140.