Schema forbids booleans for `version_removed`, but data contains `false` values

[ddbeck]

What type of issue is this?

Other

What information was incorrect, unhelpful, or incomplete?

The schema describes version_removed as an optional property with a string value:

browser-compat-data/schemas/compat-data.schema.json

Lines 21 to 26 in 79a5bf9

	"version_removed": {
	"description": "A string, indicating which browser version removed this feature.",
	"type": "string",
	"pattern": "^(≤?(\\d+)(\\.\\d+)*|preview)$",
	"tsType": "VersionValue"
	},

But at least 79 support statements contain version_removed: false. For example, running jq .api.AbortSignal.timeout_static.__compat.support.oculus build/data.json from the main branch (after npm install) yields:

{
  "notes": "Always aborts with an <code>AbortError</code> on timeout, not a <code>TimeoutError</code>.",
  "partial_implementation": true,
  "version_added": "23.0",
  "version_removed": false
}

Note: There's a secondary issue that the exported TypeScript type VersionValue is not the same as the type described by the schema. If you'd like me to file a separate issue for that, please let me know.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Safari

What did you expect to see?

I expected to see data like this:

{
  "notes": "Always aborts with an <code>AbortError</code> on timeout, not a <code>TimeoutError</code>.",
  "partial_implementation": true,
  "version_added": "23.0",
}

Did you test this? If so, how?

See my jq command for reproduction steps. Or grep it yourself.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

There is no corresponding "version_removed": false in the source files, which makes me think that this is caused by mirroring. Unfortunately, there's no way to confirm this with the published data; see #27363 for further discussion of this problem.

MDN URL

No response

MDN metadata

No response

[ddbeck]

@Elchi3 there's still the problem that the exported TypeScript type also does not match the schema, which #27451 does not resolve (basically nothing matched schema). I can file a separate issue for this, if needed, but this is still a bug. I still can't (easily) delete any version_removed: false-handling consumer code until the actual data, the schema, and the exported types line up.

[caugner]

With #27451 landed, and #27685 revealing no remaining issues, we can consider this resolved.

Thanks for raising this, Daniel. 🙌