feat(schemas/browser)!: changes releases from object to array

[caugner]

Summary

Breaking change: Changes the browsers.*.releases property from an object to an array, moving the version number inside the ReleaseStatement.

Test results and supporting details

Related issues

Fixes #21124.

[queengooborg]

Honestly, I'd love to try and find an alternate solution if we can. I feel that since consumers can access the order through other means (either comparing version numbers or release dates, depending on their use of Node.js data), I'm cautiously skeptical about changing the data structure this much.

[ddbeck]

@queengooborg In #21124, I put forward some alternatives, which have their own share of difficulties. It'd be helpful if you could read and respond to the inciting issue.

@caugner one thing Philip raised as a possibility on the original issue is tests that assert that "dates are strictly increasing and that the order matches that which compare-versions produces." Would it be too much to ask to add these tests? I think both of these would be a good idea, to make explicit the assumptions that we've held historically and relied on to transform the objects to arrays.

[caugner]

assert that "dates are strictly increasing and that the order matches that which compare-versions produces."

@ddbeck If I understand you correctly, then this assumption already doesn't hold for Node.js releases:

• v20.17.0 was released on 2024-08-21
• v21.0.0 was released on 2023-10-17

We could enforce it for other browsers, though, if that's an acceptable compromise from your side?

@Elchi3 What's your opinion here?

[Elchi3]

I think that would be a good enforcement and if we need to exclude nodejs from that rule, that's okay, too.