fix: update json-schema

[viceice]

Changes

• Allow ^regex:.* as versioning
• Add description to global array objects (like packageRules or regexManagers)

Context

• fixes Allow regex:* strings in versioning for JSON schema #22249

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

1054a1055,1058
>               "description": {
>                 "type": "string",
>                 "description": "A custom description"
>               },
1553a1558,1561
>               "description": {
>                 "type": "string",
>                 "description": "A custom description"
>               },
2069a2078,2081
>               "description": {
>                 "type": "string",
>                 "description": "A custom description"
>               },
2329a2342,2345
>               "description": {
>                 "type": "string",
>                 "description": "A custom description"
>               },
2748,2784c2764,2808
<       "enum": [
<         "aws-machine-image",
<         "azure-rest-api",
<         "bazel-module",
<         "cargo",
<         "composer",
<         "conan",
<         "deb",
<         "debian",
<         "docker",
<         "git",
<         "go-mod-directive",
<         "gradle",
<         "hashicorp",
<         "helm",
<         "hermit",
<         "hex",
<         "ivy",
<         "kubernetes-api",
<         "loose",
<         "maven",
<         "nixpkgs",
<         "node",
<         "npm",
<         "nuget",
<         "pep440",
<         "perl",
<         "poetry",
<         "python",
<         "redhat",
<         "regex",
<         "rez",
<         "ruby",
<         "semver",
<         "semver-coerced",
<         "swift",
<         "ubuntu"
---
>       "oneOf": [
>         {
>           "enum": [
>             "aws-machine-image",
>             "azure-rest-api",
>             "bazel-module",
>             "cargo",
>             "composer",
>             "conan",
>             "deb",
>             "debian",
>             "docker",
>             "git",
>             "go-mod-directive",
>             "gradle",
>             "hashicorp",
>             "helm",
>             "hermit",
>             "hex",
>             "ivy",
>             "kubernetes-api",
>             "loose",
>             "maven",
>             "nixpkgs",
>             "node",
>             "npm",
>             "nuget",
>             "pep440",
>             "perl",
>             "poetry",
>             "python",
>             "redhat",
>             "regex",
>             "rez",
>             "ruby",
>             "semver",
>             "semver-coerced",
>             "swift",
>             "ubuntu"
>           ]
>         },
>         {
>           "type": "string",
>           "pattern": "^regex:"
>         }

[rarkins]

@viceice I don't understand this "a custom description" change. Here's an example:

    "hostRules": {
      "description": "Host rules/configuration including credentials.",
      "type": "array",
      "items": {
        "allOf": [
          {
            "type": "object",
            "properties": {
              "description": {
                "type": "string",
                "description": "A custom description"
              },
              "abortIgnoreStatusCodes": {
                "description": "A list of HTTP status codes safe to ignore even when `abortOnError=true`.",
                "type": "array",
                "items": {
                  "type": "number"
                }
              },

[viceice]

it adds the description field to the schema, which we already heavily use to describe package rules. so the editor can suggest that field now.

[viceice]

i can change the description of the description property, it seems to confusing 😬

[viceice]

@viceice I don't understand this "a custom description" change. Here's an example:

    "hostRules": {
      "description": "Host rules/configuration including credentials.",
      "type": "array",
      "items": {
        "allOf": [
          {
            "type": "object",
            "properties": {
              "description": {
                "type": "string",
                "description": "A custom description"
              },
              "abortIgnoreStatusCodes": {
                "description": "A list of HTTP status codes safe to ignore even when `abortOnError=true`.",
                "type": "array",
                "items": {
                  "type": "number"
                }
              },

description is added for child objects of these root properties:

[renovate-release]

🎉 This PR is included in version 35.90.0 🎉

The release is available on:

• GitHub release
• 35.90.0

Your semantic-release bot 📦🚀