Include version in data.json

[foolip]

To allow consumers to avoid upgrading to a new major version while using GitHub releases, let's put the version itself in the data.json, like BCD does:

https://github.com/mdn/browser-compat-data/blob/d6fbc4b859d1bff8216caae03cef22c3afe8e157/README.md#__meta

Discussed with @jcscottiii

[captainbrosset]

I would like this too! I have a piece of code in an 11ty build config file that I use to do this:

const { default: webFeaturesPackageJson } = await import("./node_modules/web-features/package.json", {
  assert: { type: "json" },
});

const versions = {
  "webFeatures": webFeaturesPackageJson.version,
  "bcd": bcd.__meta.version
};

Much much easier to do it for BCD at the moment. So doing something similar would be great.

[foolip]

Let's do this in the same release that adds groups, so that we have something like:

{
  "features": {},
  "groups": {},
  "__meta": {
    "version": "0.9.0"
  }
}

[ddbeck]

In the WebDX call today, it was suggested that we could include the browser compat data version (and maybe date?) in the meta object as well.

Something like this, perhaps?

{
  "features": {},
  "groups": {},
  "__meta": {
    "version": "0.9.0",
    "last_updated": "2024-06-27",
    "@mdn/browser-compat-data": "v5.5.35",
  }
}