api.github.com

When I fetch the latest from https://github.com/github/rest-api-description (it has the same version but it is not the same api), I encounter the following five parse errors. yes, there are only five.

1. fails in typify schemas_mutually_exclusive due to this field.

"conditions": {
            "anyOf": [
              {
                "$ref": "#/components/schemas/repository-ruleset-conditions"
              },
              {
                "$ref": "#/components/schemas/org-ruleset-conditions"
              }
            ]
          },

2. /markdown/raw handles two media types , text/plain and text/x-markdown .
3. Fails due to this:

"422": {
            "description": "Validation failed",
            "content": {
              "application/json": {
                "schema": {
                  "oneOf": [
                    {
                      "$ref": "#/components/schemas/validation-error"
                    },
                    {
                      "$ref": "#/components/schemas/validation-error-simple"
                    }
                  ]
                }
              }
            }
          },

4. Fails due to this

                  "make_latest": {
                    "type": "string",
                    "description": "Specifies whether this release should be set as the latest release for the repository. Drafts and prereleases cannot be set as latest. Defaults to `true` for newly published releases. `legacy` specifies that the latest release should be determined based on the release creation date and higher semantic version.",
                    "enum": [
                      "true",
                      "false",
                      "legacy"
                    ],
                    "default": true
                  },

5. response_types.len() <= 1', progenitor-impl/src/method.rs:1171:9 https://github.com/oxidecomputer/progenitor/issues/344

Reproduce generation against the latest github/rest-api-description and inspect the five parse failures listed in the issue. Start with progenitor-impl/src/method.rs at the reported response_types assertion, then trace the other schema and media-type failures; done means the specification parses and generation completes without those errors.