Update vendored schemas

Author: sirosen

CHANGELOG.rst

@@ -10,7 +10,7 @@ Unreleased
 
 .. vendor-insert-here
 
-- Update vendored schemas (2024-03-28)
+- Update vendored schemas (2024-03-31)
 
 0.28.0
 ------

src/check_jsonschema/builtin_schemas/vendor/github-actions.json

@@ -15,12 +15,12 @@
       "pattern": "^.*\\$\\{\\{(.|[\r\n])*\\}\\}.*$"
     },
     "pre-if": {
-      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#pre-if",
+      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspre-if",
       "description": "Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`. Note that the `step` context is unavailable, as no steps have run yet.",
       "type": "string"
     },
     "post-if": {
-      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#post-if",
+      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspost-if",
       "description": "Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`.",
       "type": "string"
     },
@@ -40,15 +40,15 @@
           "type": "string"
         },
         "pre": {
-          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#pre",
+          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspre",
           "description": "Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The application specified with the `using` syntax will execute this file. The `pre:` action always runs by default but you can override this using `pre-if`.",
           "type": "string"
         },
         "pre-if": {
           "$ref": "#/definitions/pre-if"
         },
         "post": {
-          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#post",
+          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspost",
           "description": "Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The application specified with the `using` syntax will execute this file. The `post:` action always runs by default but you can override this using `post-if`.",
           "type": "string"
         },
@@ -60,12 +60,12 @@
       "additionalProperties": false
     },
     "runs-composite": {
-      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-run-steps-actions",
+      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions",
       "description": "Configures the path to the composite action, and the application used to execute the code.",
       "type": "object",
       "properties": {
         "using": {
-          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-1",
+          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-for-composite-actions",
           "description": "To use a composite run steps action, set this to 'composite'.",
           "const": "composite"
         },
@@ -169,12 +169,12 @@
       "additionalProperties": false
     },
     "runs-docker": {
-      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-docker-actions",
+      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-docker-container-actions",
       "description": "Configures the image used for the Docker action.",
       "type": "object",
       "properties": {
         "using": {
-          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-2",
+          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runsusing-for-docker-container-actions",
           "description": "You must set this value to 'docker'.",
           "const": "docker"
         },
@@ -214,15 +214,15 @@
           "type": "string"
         },
         "pre-entrypoint": {
-          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#pre-entrypoint",
+          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspre-entrypoint",
           "description": "Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. GitHub Actions uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using `pre-if`.",
           "type": "string"
         },
         "pre-if": {
           "$ref": "#/definitions/pre-if"
         },
         "post-entrypoint": {
-          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#post-entrypoint",
+          "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runspost-entrypoint",
           "description": "Allows you to run a cleanup script once the `runs.entrypoint` action has completed. GitHub Actions uses `docker run` to launch this action. Because GitHub Actions runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using `post-if`.",
           "type": "string"
         },
@@ -242,7 +242,7 @@
       "additionalProperties": false
     },
     "outputs": {
-      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#outputs",
+      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions",
       "description": "Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions. For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.\nIf you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow.",
       "type": "object",
       "patternProperties": {
@@ -264,7 +264,7 @@
       "additionalProperties": false
     },
     "outputs-composite": {
-      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-run-steps-actions",
+      "$comment": "https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions",
       "description": "Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions. For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.\nIf you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow.",
       "type": "object",
       "patternProperties": {

src/check_jsonschema/builtin_schemas/vendor/github-actions.sha256

@@ -1 +1 @@
-9f0c77d226f811a208e6b0c839ae93df6848b35687d8309041504352252dbbf9
+d6da49b4fca964c06525a7a39fb9d346ba7a5ee0ed185ce8f74c7a4e91c7b6c7

src/check_jsonschema/builtin_schemas/vendor/woodpecker-ci.json

@@ -696,6 +696,10 @@
         },
         "securityContext": {
           "$ref": "#/definitions/step_backend_kubernetes_security_context"
+        },
+        "runtimeClassName": {
+          "description": "Read more: https://woodpecker-ci.org/docs/administration/backends/kubernetes#runtimeclassname",
+          "type": "string"
         }
       }
     },

src/check_jsonschema/builtin_schemas/vendor/woodpecker-ci.sha256

@@ -1 +1 @@
-7444b00a35523cab51e91aaed69c20e4e9c402d1ebb684ae04625ac692e12504
+f486bb80b1e502f01bf6d718eef1530501fbeca043f768bae5fe50779d437185