Queen Vinyl Da.i'gyu-Kazotetsu

+1 for this -- having an automated maintenance process for new browser releases would be very helpful!

This has been added as a Q3 project (with myself as the assignee)!

> There's also beta releases, which is mostly a matter of changing those dates. I don't think we should collect results for beta browser versions, for the very same reason...

I actually don't have editor access for this repository, so I can't add labels!

@jpmedley It's not, and that is all the more reason why this project would be helpful. By mirroring the majority of the Chromium data over to the derivative browsers, such...

Phase one of this project has now been implemented in https://github.com/mdn/browser-compat-data/pull/16401! There are some bugs to work out before we perform a mass conversion of existing data to use mirroring....

Oh wow, looks like this has pretty much entirely been taken care of now for the English locale -- the only file left will be removed in https://github.com/mdn/content/pull/18778!

Hey @aeschli! I would recommend obtaining status data from the `@mdn/browser-compat-data` package instead, as it is actively maintained -- see https://github.com/mdn/browser-compat-data/blob/b3c2cbc32fc2695b58545e7c764cd56eaca4d98c/css/properties/aspect-ratio.json#L84-L88 for the relevant information.

Certainly -- here's the above example put into a runnable script to show the issue: ```js import { compile } from 'json-schema-to-typescript'; const opts = { bannerComment: '', unreachableDefinitions: true,...

Update: it seems that `unreachableDefinitions: true` causes this issue, as switching it to `false` will generate the expected typedefs. However, because we define custom `tsType`s, disabling the option is not...