Skip to content

Commit 99708b6

Browse files
[vendor-schemas] automated update (#189)
Co-authored-by: sirosen <[email protected]>
1 parent 97b117d commit 99708b6

File tree

3 files changed

+94
-88
lines changed

3 files changed

+94
-88
lines changed

CHANGELOG.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ Unreleased
1010

1111
.. vendor-insert-here
1212
13+
- Update vendored schemas (2022-11-22)
14+
1315
0.19.2
1416
------
1517

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

Lines changed: 91 additions & 87 deletions
Original file line numberDiff line numberDiff line change
@@ -701,106 +701,110 @@
701701
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps",
702702
"description": "A job contains a sequence of tasks called steps. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the virtual environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. GitHub provides built-in steps to set up and complete a job.\nMust contain either `uses` or `run`\n",
703703
"type": "array",
704-
"contains": {
705-
"oneOf": [
704+
"items": {
705+
"allOf": [
706706
{
707-
"type": "object",
708-
"properties": {
709-
"uses": {
710-
"type": "string"
707+
"oneOf": [
708+
{
709+
"type": "object",
710+
"properties": {
711+
"uses": {
712+
"type": "string"
713+
}
714+
},
715+
"required": ["uses"]
716+
},
717+
{
718+
"type": "object",
719+
"properties": {
720+
"run": {
721+
"type": "string"
722+
}
723+
},
724+
"required": ["run"]
711725
}
712-
},
713-
"required": ["uses"]
726+
]
714727
},
715728
{
716729
"type": "object",
717730
"properties": {
718-
"run": {
731+
"id": {
732+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid",
733+
"description": "A unique identifier for the step. You can use the id to reference the step in contexts. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.",
719734
"type": "string"
720-
}
721-
},
722-
"required": ["run"]
723-
}
724-
]
725-
},
726-
"items": {
727-
"type": "object",
728-
"properties": {
729-
"id": {
730-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid",
731-
"description": "A unique identifier for the step. You can use the id to reference the step in contexts. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.",
732-
"type": "string"
733-
},
734-
"if": {
735-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsif",
736-
"description": "You can use the if conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.\nExpressions in an if conditional do not require the ${{ }} syntax. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.",
737-
"type": ["boolean", "number", "string"]
738-
},
739-
"name": {
740-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsname",
741-
"description": "A name for your step to display on GitHub.",
742-
"type": "string"
743-
},
744-
"uses": {
745-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsuses",
746-
"description": "Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a published Docker container image (https://hub.docker.com/).\nWe strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.\n- Using the commit SHA of a released action version is the safest for stability and security.\n- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.\n- Using the master branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.\nSome actions require inputs that you must set using the with keyword. Review the action's README file to determine the inputs required.\nActions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux virtual environment. For more details, see https://help.github.com/en/articles/virtual-environments-for-github-actions.",
747-
"type": "string"
748-
},
749-
"run": {
750-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsrun",
751-
"description": "Runs command-line programs using the operating system's shell. If you do not provide a name, the step name will default to the text specified in the run command.\nCommands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell.\nEach run keyword represents a new process and shell in the virtual environment. When you provide multi-line commands, each line runs in the same shell.",
752-
"type": "string"
753-
},
754-
"working-directory": {
755-
"$ref": "#/definitions/working-directory"
756-
},
757-
"shell": {
758-
"$ref": "#/definitions/shell"
759-
},
760-
"with": {
761-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswith",
762-
"$ref": "#/definitions/env",
763-
"description": "A map of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with INPUT_ and converted to upper case.",
764-
"properties": {
765-
"args": {
766-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswithargs",
735+
},
736+
"if": {
737+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsif",
738+
"description": "You can use the if conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.\nExpressions in an if conditional do not require the ${{ }} syntax. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.",
739+
"type": ["boolean", "number", "string"]
740+
},
741+
"name": {
742+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsname",
743+
"description": "A name for your step to display on GitHub.",
767744
"type": "string"
768745
},
769-
"entrypoint": {
770-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswithentrypoint",
746+
"uses": {
747+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsuses",
748+
"description": "Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a published Docker container image (https://hub.docker.com/).\nWe strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.\n- Using the commit SHA of a released action version is the safest for stability and security.\n- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.\n- Using the master branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.\nSome actions require inputs that you must set using the with keyword. Review the action's README file to determine the inputs required.\nActions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux virtual environment. For more details, see https://help.github.com/en/articles/virtual-environments-for-github-actions.",
771749
"type": "string"
772-
}
773-
}
774-
},
775-
"env": {
776-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv",
777-
"$ref": "#/definitions/env",
778-
"description": "Sets environment variables for steps to use in the virtual environment. You can also set environment variables for the entire workflow or a job."
779-
},
780-
"continue-on-error": {
781-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error",
782-
"description": "Prevents a job from failing when a step fails. Set to true to allow a job to pass when this step fails.",
783-
"oneOf": [
784-
{
785-
"type": "boolean"
786750
},
787-
{
788-
"$ref": "#/definitions/expressionSyntax"
751+
"run": {
752+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsrun",
753+
"description": "Runs command-line programs using the operating system's shell. If you do not provide a name, the step name will default to the text specified in the run command.\nCommands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#using-a-specific-shell.\nEach run keyword represents a new process and shell in the virtual environment. When you provide multi-line commands, each line runs in the same shell.",
754+
"type": "string"
755+
},
756+
"working-directory": {
757+
"$ref": "#/definitions/working-directory"
758+
},
759+
"shell": {
760+
"$ref": "#/definitions/shell"
761+
},
762+
"with": {
763+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswith",
764+
"$ref": "#/definitions/env",
765+
"description": "A map of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with INPUT_ and converted to upper case.",
766+
"properties": {
767+
"args": {
768+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswithargs",
769+
"type": "string"
770+
},
771+
"entrypoint": {
772+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswithentrypoint",
773+
"type": "string"
774+
}
775+
}
776+
},
777+
"env": {
778+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv",
779+
"$ref": "#/definitions/env",
780+
"description": "Sets environment variables for steps to use in the virtual environment. You can also set environment variables for the entire workflow or a job."
781+
},
782+
"continue-on-error": {
783+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error",
784+
"description": "Prevents a job from failing when a step fails. Set to true to allow a job to pass when this step fails.",
785+
"oneOf": [
786+
{
787+
"type": "boolean"
788+
},
789+
{
790+
"$ref": "#/definitions/expressionSyntax"
791+
}
792+
],
793+
"default": false
794+
},
795+
"timeout-minutes": {
796+
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes",
797+
"description": "The maximum number of minutes to run the step before killing the process.",
798+
"type": "number"
789799
}
790-
],
791-
"default": false
792-
},
793-
"timeout-minutes": {
794-
"$comment": "https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes",
795-
"description": "The maximum number of minutes to run the step before killing the process.",
796-
"type": "number"
800+
},
801+
"dependencies": {
802+
"working-directory": ["run"],
803+
"shell": ["run"]
804+
},
805+
"additionalProperties": false
797806
}
798-
},
799-
"dependencies": {
800-
"working-directory": ["run"],
801-
"shell": ["run"]
802-
},
803-
"additionalProperties": false
807+
]
804808
},
805809
"minItems": 1
806810
},
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
916f3ee9283f7977460f5e6a1323585a03006d46b21bed0e3001d411c63acfcc
1+
3d52d4f7e5da7e1fb60c9ae665891585b0c79a3b0681ef849f09b8eafbd64f15

0 commit comments

Comments
 (0)