@bensandee/tooling 0.93.0 → 0.93.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/bin.mjs +52 -31
  2. package/package.json +1 -1
package/dist/bin.mjs CHANGED
@@ -175,7 +175,7 @@ function loadEnvFileForBin(rawArgs, bin, io = processIo) {
175
175
  //#region src/env-file-preload.ts
176
176
  const envFileLoad = loadEnvFileForBin(process.argv.slice(2), {
177
177
  name: "bst",
178
- version: "0.93.0"
178
+ version: "0.93.1"
179
179
  });
180
180
  //#endregion
181
181
  //#region ../cli-kit/src/logger.ts
@@ -4944,6 +4944,11 @@ function readUnmanagedDevDepNames(ctx) {
4944
4944
  const slice = parseToolingConfigSlice(ctx.read(".tooling.json"), UnmanagedSliceSchema, { block: "unmanagedDevDependencies" });
4945
4945
  return new Set(slice?.unmanagedDevDependencies ?? []);
4946
4946
  }
4947
+ const COMMIT_AND_TAG_VERSION_PACKAGE = "commit-and-tag-version";
4948
+ function wantsCommitAndTagVersion(ctx) {
4949
+ if (ctx.config.releaseStrategy !== "simple") return false;
4950
+ return !readUnmanagedDevDepNames(ctx).has(COMMIT_AND_TAG_VERSION_PACKAGE);
4951
+ }
4947
4952
  //#endregion
4948
4953
  //#region src/generators/package-json.ts
4949
4954
  const NODE_ENGINES_FLOOR = "24.13.0";
@@ -5231,8 +5236,8 @@ function rootDevDeps(config) {
5231
5236
  }["oxlint-tsgolint"];
5232
5237
  return deps;
5233
5238
  }
5234
- function addReleaseDeps(deps, config) {
5235
- switch (config.releaseStrategy) {
5239
+ function addReleaseDeps(deps, ctx) {
5240
+ switch (ctx.config.releaseStrategy) {
5236
5241
  case "release-it":
5237
5242
  deps["release-it"] = {
5238
5243
  "@changesets/cli": "3.0.3",
@@ -5253,7 +5258,7 @@ function addReleaseDeps(deps, config) {
5253
5258
  "vitest": "5.0.3",
5254
5259
  "pnpm": "11.28.5"
5255
5260
  }["release-it"];
5256
- if (config.structure === "monorepo") deps["@release-it/bumper"] = {
5261
+ if (ctx.config.structure === "monorepo") deps["@release-it/bumper"] = {
5257
5262
  "@changesets/cli": "3.0.3",
5258
5263
  "@release-it/bumper": "8.0.1",
5259
5264
  "@types/node": "24.19.1",
@@ -5274,7 +5279,7 @@ function addReleaseDeps(deps, config) {
5274
5279
  }["@release-it/bumper"];
5275
5280
  break;
5276
5281
  case "simple":
5277
- deps["commit-and-tag-version"] = {
5282
+ if (wantsCommitAndTagVersion(ctx)) deps[COMMIT_AND_TAG_VERSION_PACKAGE] = {
5278
5283
  "@changesets/cli": "3.0.3",
5279
5284
  "@release-it/bumper": "8.0.1",
5280
5285
  "@types/node": "24.19.1",
@@ -5477,8 +5482,8 @@ function buildManagedDevDeps(ctx) {
5477
5482
  const isMonorepo = ctx.config.structure === "monorepo";
5478
5483
  const devDeps = { ...rootDevDeps(ctx.config) };
5479
5484
  if (!isMonorepo) Object.assign(devDeps, perPackageDevDeps(ctx.config));
5480
- if (ctx.config.stack !== "none" || ctx.config.ci === "forgejo") devDeps["@bensandee/config"] = isWorkspacePackage(ctx, "@bensandee/config") ? "workspace:*" : "0.15.0";
5481
- if (!isWorkspacePackage(ctx, "@bensandee/tooling")) devDeps["@bensandee/tooling"] = "0.93.0";
5485
+ if (ctx.config.stack !== "none") devDeps["@bensandee/config"] = isWorkspacePackage(ctx, "@bensandee/config") ? "workspace:*" : "0.15.0";
5486
+ if (!isWorkspacePackage(ctx, "@bensandee/tooling")) devDeps["@bensandee/tooling"] = "0.93.1";
5482
5487
  if (ctx.config.useEslintPlugin && ctx.config.stack !== "none") devDeps["@bensandee/eslint-plugin"] = isWorkspacePackage(ctx, "@bensandee/eslint-plugin") ? "workspace:*" : "0.17.0";
5483
5488
  if (wantsAgentCli(ctx)) devDeps[AGENT_CLI_PACKAGE] = "0.1.2";
5484
5489
  if (ctx.config.formatter === "oxfmt") devDeps["oxfmt"] = {
@@ -5519,7 +5524,7 @@ function buildManagedDevDeps(ctx) {
5519
5524
  "vitest": "5.0.3",
5520
5525
  "pnpm": "11.28.5"
5521
5526
  }["prettier"];
5522
- addReleaseDeps(devDeps, ctx.config);
5527
+ addReleaseDeps(devDeps, ctx);
5523
5528
  return devDeps;
5524
5529
  }
5525
5530
  async function generatePackageJson(ctx) {
@@ -7994,7 +7999,10 @@ function ignoreBinariesField(binaries) {
7994
7999
  return binaries.length > 0 ? `\n ignoreBinaries: ${JSON.stringify(binaries)},` : "";
7995
8000
  }
7996
8001
  function ignorableDependencies(ctx) {
7997
- return wantsAgentCli(ctx) ? [AGENT_CLI_PACKAGE] : [];
8002
+ const dependencies = [];
8003
+ if (wantsAgentCli(ctx)) dependencies.push(AGENT_CLI_PACKAGE);
8004
+ if (wantsCommitAndTagVersion(ctx)) dependencies.push(COMMIT_AND_TAG_VERSION_PACKAGE);
8005
+ return dependencies;
7998
8006
  }
7999
8007
  function ignoreDependenciesField(dependencies) {
8000
8008
  return dependencies.length > 0 ? `\n ignoreDependencies: ${JSON.stringify(dependencies)},` : "";
@@ -8003,7 +8011,6 @@ function buildKnipConfigSingle(ignoreBinaries, ignoreDependencies) {
8003
8011
  return `import type { KnipConfig } from "knip";
8004
8012
 
8005
8013
  export default {
8006
- entry: ["src/index.ts"],
8007
8014
  project: ["src/**/*.ts"],${ignoreBinariesField(ignoreBinaries)}${ignoreDependenciesField(ignoreDependencies)}
8008
8015
  } satisfies KnipConfig;
8009
8016
  `;
@@ -8018,7 +8025,6 @@ export default {${ignoreBinariesField(ignoreBinaries)}${ignoreDependenciesField(
8018
8025
  project: [],
8019
8026
  },
8020
8027
  "packages/*": {
8021
- entry: ["src/index.ts", "src/bin.ts"],
8022
8028
  project: ["src/**/*.ts"],
8023
8029
  },
8024
8030
  },
@@ -8851,16 +8857,10 @@ async function generateLefthook(ctx) {
8851
8857
  }
8852
8858
  //#endregion
8853
8859
  //#region src/generators/vscode-settings.ts
8854
- const SCHEMA_NPM_PATH = "@bensandee/config/schemas/forgejo-workflow.schema.json";
8855
8860
  const SCHEMA_LOCAL_PATH = ".vscode/forgejo-workflow.schema.json";
8856
8861
  const SETTINGS_PATH = ".vscode/settings.json";
8857
8862
  const SCHEMA_GLOB = ".forgejo/workflows/*.{yml,yaml}";
8858
8863
  const VscodeSettingsSchema = z.looseObject({ "yaml.schemas": z.record(z.string(), z.unknown()).default({}) });
8859
- function readSchemaFromNodeModules(targetDir) {
8860
- const candidate = path.join(targetDir, "node_modules", SCHEMA_NPM_PATH);
8861
- if (!existsSync(candidate)) return void 0;
8862
- return readFileSync(candidate, "utf-8");
8863
- }
8864
8864
  function serializeSettings(settings) {
8865
8865
  return JSON.stringify(settings, null, 2) + "\n";
8866
8866
  }
@@ -8927,15 +8927,7 @@ async function generateVscodeSettings(ctx) {
8927
8927
  });
8928
8928
  return results;
8929
8929
  }
8930
- const schemaContent = readSchemaFromNodeModules(ctx.targetDir);
8931
- if (!schemaContent) {
8932
- results.push({
8933
- filePath: SCHEMA_LOCAL_PATH,
8934
- action: "skipped",
8935
- description: "Could not find @bensandee/config schema in node_modules"
8936
- });
8937
- return results;
8938
- }
8930
+ const schemaContent = "{\n \"$schema\": \"http://json-schema.org/draft-07/schema#\",\n \"$comment\": \"GitHub Actions workflow schema extended with Forgejo-specific properties\",\n \"additionalProperties\": false,\n \"definitions\": {\n \"architecture\": {\n \"type\": \"string\",\n \"enum\": [\"ARM32\", \"x64\", \"x86\"]\n },\n \"branch\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestbranchestags\",\n \"$ref\": \"#/definitions/globs\",\n \"description\": \"When using the push and pull_request events, you can configure a workflow to run on specific branches or tags. If you only define only tags or only branches, the workflow won't run for events affecting the undefined Git ref.\\nThe branches, branches-ignore, tags, and tags-ignore keywords accept glob patterns that use the * and ** wildcard characters to match more than one branch or tag name. For more information, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet.\\nThe patterns defined in branches and tags are evaluated against the Git ref's name. For example, defining the pattern mona/octocat in branches will match the refs/heads/mona/octocat Git ref. The pattern releases/** will match the refs/heads/releases/10 Git ref.\\nYou can use two types of filters to prevent a workflow from running on pushes and pull requests to tags and branches:\\n- branches or branches-ignore - You cannot use both the branches and branches-ignore filters for the same event in a workflow. Use the branches filter when you need to filter branches for positive matches and exclude branches. Use the branches-ignore filter when you only need to exclude branch names.\\n- tags or tags-ignore - You cannot use both the tags and tags-ignore filters for the same event in a workflow. Use the tags filter when you need to filter tags for positive matches and exclude tags. Use the tags-ignore filter when you only need to exclude tag names.\\nYou can exclude tags and branches using the ! character. The order that you define patterns matters.\\n- A matching negative pattern (prefixed with !) after a positive match will exclude the Git ref.\\n- A matching positive pattern after a negative match will include the Git ref again.\"\n },\n \"concurrency\": {\n \"type\": \"object\",\n \"properties\": {\n \"group\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-using-concurrency-to-cancel-any-in-progress-job-or-run-1\",\n \"description\": \"When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled.\",\n \"type\": \"string\"\n },\n \"cancel-in-progress\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-using-concurrency-to-cancel-any-in-progress-job-or-run-1\",\n \"description\": \"To cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.\",\n \"oneOf\": [\n {\n \"type\": \"boolean\"\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ]\n }\n },\n \"required\": [\"group\"],\n \"additionalProperties\": false\n },\n \"configuration\": {\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"type\": \"number\"\n },\n {\n \"type\": \"boolean\"\n },\n {\n \"type\": \"object\",\n \"additionalProperties\": {\n \"$ref\": \"#/definitions/configuration\"\n }\n },\n {\n \"type\": \"array\",\n \"items\": {\n \"$ref\": \"#/definitions/configuration\"\n }\n }\n ]\n },\n \"container\": {\n \"type\": \"object\",\n \"properties\": {\n \"image\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainerimage\",\n \"description\": \"The Docker image to use as the container to run the action. The value can be the Docker Hub image name or a registry name.\",\n \"type\": \"string\"\n },\n \"credentials\": {\n \"$comment\": \"https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainercredentials\",\n \"description\": \"If the image's container registry requires authentication to pull the image, you can use credentials to set a map of the username and password. The credentials are the same values that you would provide to the `docker login` command.\",\n \"type\": \"object\",\n \"properties\": {\n \"username\": {\n \"type\": \"string\"\n },\n \"password\": {\n \"type\": \"string\"\n }\n }\n },\n \"env\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainerenv\",\n \"$ref\": \"#/definitions/env\",\n \"description\": \"Sets an array of environment variables in the container.\"\n },\n \"ports\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainerports\",\n \"description\": \"Sets an array of ports to expose on the container.\",\n \"type\": \"array\",\n \"items\": {\n \"oneOf\": [\n {\n \"type\": \"number\"\n },\n {\n \"type\": \"string\"\n }\n ]\n },\n \"minItems\": 1\n },\n \"volumes\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainervolumes\",\n \"description\": \"Sets an array of volumes for the container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.\\nTo specify a volume, you specify the source and destination path: <source>:<destinationPath>\\nThe <source> is a volume name or an absolute path on the host machine, and <destinationPath> is an absolute path in the container.\",\n \"type\": \"array\",\n \"items\": {\n \"type\": \"string\"\n },\n \"minItems\": 1\n },\n \"options\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontaineroptions\",\n \"description\": \"Additional Docker container resource options. For a list of options, see https://docs.docker.com/engine/reference/commandline/create/#options.\",\n \"type\": \"string\"\n }\n },\n \"required\": [\"image\"],\n \"additionalProperties\": false\n },\n \"defaults\": {\n \"type\": \"object\",\n \"properties\": {\n \"run\": {\n \"type\": \"object\",\n \"properties\": {\n \"shell\": {\n \"$ref\": \"#/definitions/shell\"\n },\n \"working-directory\": {\n \"$ref\": \"#/definitions/working-directory\"\n }\n },\n \"minProperties\": 1,\n \"additionalProperties\": false\n }\n },\n \"minProperties\": 1,\n \"additionalProperties\": false\n },\n \"permissions\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#permissions\",\n \"description\": \"You can modify the default permissions granted to the GITHUB_TOKEN, adding or removing access as required, so that you only allow the minimum required access.\",\n \"oneOf\": [\n {\n \"type\": \"string\",\n \"enum\": [\"read-all\", \"write-all\"]\n },\n {\n \"$ref\": \"#/definitions/permissions-event\"\n }\n ]\n },\n \"permissions-event\": {\n \"type\": \"object\",\n \"additionalProperties\": false,\n \"properties\": {\n \"actions\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"artifact-metadata\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"attestations\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"checks\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"contents\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"deployments\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"discussions\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"id-token\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"issues\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"models\": {\n \"type\": \"string\",\n \"enum\": [\"read\", \"none\"]\n },\n \"packages\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"pages\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"pull-requests\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"repository-projects\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"security-events\": {\n \"$ref\": \"#/definitions/permissions-level\"\n },\n \"statuses\": {\n \"$ref\": \"#/definitions/permissions-level\"\n }\n }\n },\n \"permissions-level\": {\n \"type\": \"string\",\n \"enum\": [\"read\", \"write\", \"none\"]\n },\n \"env\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/environment-variables\",\n \"description\": \"To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the jobs.<job_id>.steps[*].env, jobs.<job_id>.env, and env keywords. For more information, see https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv\",\n \"oneOf\": [\n {\n \"type\": \"object\",\n \"additionalProperties\": {\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"type\": \"number\"\n },\n {\n \"type\": \"boolean\"\n }\n ]\n }\n },\n {\n \"$ref\": \"#/definitions/stringContainingExpressionSyntax\"\n }\n ]\n },\n \"environment\": {\n \"$comment\": \"https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#jobsjob_idenvironment\",\n \"description\": \"The environment that the job references\",\n \"type\": \"object\",\n \"properties\": {\n \"name\": {\n \"$comment\": \"https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#example-using-a-single-environment-name\",\n \"description\": \"The name of the environment configured in the repo.\",\n \"type\": \"string\"\n },\n \"url\": {\n \"$comment\": \"https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#example-using-environment-name-and-url\",\n \"description\": \"A deployment URL\",\n \"type\": \"string\"\n }\n },\n \"required\": [\"name\"],\n \"additionalProperties\": false\n },\n \"event\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows\",\n \"type\": \"string\",\n \"enum\": [\n \"branch_protection_rule\",\n \"check_run\",\n \"check_suite\",\n \"create\",\n \"delete\",\n \"deployment\",\n \"deployment_status\",\n \"discussion\",\n \"discussion_comment\",\n \"fork\",\n \"gollum\",\n \"issue_comment\",\n \"issues\",\n \"label\",\n \"merge_group\",\n \"milestone\",\n \"page_build\",\n \"project\",\n \"project_card\",\n \"project_column\",\n \"public\",\n \"pull_request\",\n \"pull_request_review\",\n \"pull_request_review_comment\",\n \"pull_request_target\",\n \"push\",\n \"registry_package\",\n \"release\",\n \"status\",\n \"watch\",\n \"workflow_call\",\n \"workflow_dispatch\",\n \"workflow_run\",\n \"repository_dispatch\"\n ]\n },\n \"eventObject\": {\n \"oneOf\": [\n {\n \"type\": \"object\"\n },\n {\n \"type\": \"null\"\n }\n ],\n \"additionalProperties\": true\n },\n \"expressionSyntax\": {\n \"$comment\": \"escape `{` and `}` in pattern to be unicode compatible (#1360)\",\n \"type\": \"string\",\n \"pattern\": \"^\\\\$\\\\{\\\\{(.|[\\r\\n])*\\\\}\\\\}$\"\n },\n \"stringContainingExpressionSyntax\": {\n \"$comment\": \"escape `{` and `}` in pattern to be unicode compatible (#1360)\",\n \"type\": \"string\",\n \"pattern\": \"^.*\\\\$\\\\{\\\\{(.|[\\r\\n])*\\\\}\\\\}.*$\"\n },\n \"globs\": {\n \"type\": \"array\",\n \"items\": {\n \"type\": \"string\",\n \"minLength\": 1\n },\n \"minItems\": 1\n },\n \"machine\": {\n \"type\": \"string\",\n \"enum\": [\"linux\", \"macos\", \"windows\"]\n },\n \"name\": {\n \"type\": \"string\",\n \"pattern\": \"^[_a-zA-Z][a-zA-Z0-9_-]*$\"\n },\n \"path\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths\",\n \"$ref\": \"#/definitions/globs\",\n \"description\": \"When using the push and pull_request events, you can configure a workflow to run when at least one file does not match paths-ignore or at least one modified file matches the configured paths. Path filters are not evaluated for pushes to tags.\\nThe paths-ignore and paths keywords accept glob patterns that use the * and ** wildcard characters to match more than one path name. For more information, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet.\\nYou can exclude paths using two types of filters. You cannot use both of these filters for the same event in a workflow.\\n- paths-ignore - Use the paths-ignore filter when you only need to exclude path names.\\n- paths - Use the paths filter when you need to filter paths for positive matches and exclude paths.\"\n },\n \"shell\": {\n \"$comment\": \"https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell\",\n \"description\": \"You can override the default shell settings in the runner's operating system using the shell keyword. You can use built-in shell keywords, or you can define a custom set of shell options.\",\n \"anyOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"$comment\": \"https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#custom-shell\",\n \"type\": \"string\",\n \"enum\": [\"bash\", \"pwsh\", \"python\", \"sh\", \"cmd\", \"powershell\"]\n }\n ]\n },\n \"snapshot\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#jobsjob_idsnapshot\",\n \"description\": \"You can use `jobs.<job_id>.snapshot` to generate a custom image.\\nAdd the snapshot keyword to the job, using either the string syntax or mapping syntax as shown in https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images#generating-a-custom-image.\\nEach job that includes the snapshot keyword creates a separate image. To generate only one image or image version, include all workflow steps in a single job. Each successful run of a job that includes the snapshot keyword creates a new version of that image.\\nFor more information, see https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images.\",\n \"oneOf\": [\n {\n \"$comment\": \"https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images#string-syntax\",\n \"type\": \"string\",\n \"description\": \"You can use the string syntax with `snapshot` to define the image name. This method creates a new image or adds a new version to an existing image with the same name. You cannot specify a version number using this syntax.\"\n },\n {\n \"$comment\": \"https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images#mapping-syntax\",\n \"type\": \"object\",\n \"additionalProperties\": false,\n \"description\": \"You can use the mapping syntax with `snapshot` to define both the `image-name` and the optional `version`. When you specify a major version, the minor versioning automatically increments if that major version already exists. Patch versions are not supported.\",\n \"properties\": {\n \"image-name\": {\n \"type\": \"string\"\n },\n \"version\": {\n \"$comment\": \"https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images#specifying-a-version-in-your-workflow\",\n \"type\": \"string\",\n \"pattern\": \"^\\\\d+(\\\\.\\\\d+|\\\\*)?$\"\n }\n },\n \"required\": [\"image-name\"]\n }\n ]\n },\n \"step\": {\n \"type\": \"object\",\n \"additionalProperties\": false,\n \"dependencies\": {\n \"working-directory\": [\"run\"],\n \"shell\": [\"run\"]\n },\n \"oneOf\": [\n {\n \"required\": [\"uses\"]\n },\n {\n \"required\": [\"run\"]\n }\n ],\n \"properties\": {\n \"id\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid\",\n \"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.\",\n \"type\": \"string\"\n },\n \"if\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsif\",\n \"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.\",\n \"type\": [\"boolean\", \"number\", \"string\"]\n },\n \"name\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsname\",\n \"description\": \"A name for your step to display on GitHub.\",\n \"type\": \"string\"\n },\n \"uses\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsuses\",\n \"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.\",\n \"type\": \"string\"\n },\n \"run\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsrun\",\n \"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.\",\n \"type\": \"string\"\n },\n \"working-directory\": {\n \"$ref\": \"#/definitions/working-directory\"\n },\n \"shell\": {\n \"$ref\": \"#/definitions/shell\"\n },\n \"with\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswith\",\n \"$ref\": \"#/definitions/env\",\n \"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.\",\n \"properties\": {\n \"args\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswithargs\",\n \"type\": \"string\"\n },\n \"entrypoint\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepswithentrypoint\",\n \"type\": \"string\"\n }\n }\n },\n \"env\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv\",\n \"$ref\": \"#/definitions/env\",\n \"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.\"\n },\n \"continue-on-error\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error\",\n \"description\": \"Prevents a job from failing when a step fails. Set to true to allow a job to pass when this step fails.\",\n \"oneOf\": [\n {\n \"type\": \"boolean\"\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ],\n \"default\": false\n },\n \"timeout-minutes\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes\",\n \"description\": \"The maximum number of minutes to run the step before killing the process.\",\n \"oneOf\": [\n {\n \"type\": \"number\"\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ]\n }\n }\n },\n \"types\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes\",\n \"description\": \"Selects the types of activity that will trigger a workflow run. Most GitHub events are triggered by more than one type of activity. For example, the event for the release resource is triggered when a release is published, unpublished, created, edited, deleted, or prereleased. The types keyword enables you to narrow down activity that causes the workflow to run. When only one activity type triggers a webhook event, the types keyword is unnecessary.\\nYou can use an array of event types. For more information about each event and their activity types, see https://help.github.com/en/articles/events-that-trigger-workflows#webhook-events.\",\n \"oneOf\": [\n {\n \"type\": \"array\",\n \"minItems\": 1\n },\n {\n \"type\": \"string\"\n }\n ]\n },\n \"working-directory\": {\n \"$comment\": \"https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun\",\n \"description\": \"Using the working-directory keyword, you can specify the working directory of where to run the command.\",\n \"type\": \"string\"\n },\n \"jobNeeds\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds\",\n \"description\": \"Identifies any jobs that must complete successfully before this job will run. It can be a string or array of strings. If a job fails, all jobs that need it are skipped unless the jobs use a conditional statement that causes the job to continue.\",\n \"oneOf\": [\n {\n \"type\": \"array\",\n \"items\": {\n \"$ref\": \"#/definitions/name\"\n },\n \"minItems\": 1\n },\n {\n \"$ref\": \"#/definitions/name\"\n }\n ]\n },\n \"matrix\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix\",\n \"description\": \"A build matrix is a set of different configurations of the virtual environment. For example you might run a job against more than one supported version of a language, operating system, or tool. Each configuration is a copy of the job that runs and reports a status.\\nYou can specify a matrix by supplying an array for the configuration options. For example, if the GitHub virtual environment supports Node.js versions 6, 8, and 10 you could specify an array of those versions in the matrix.\\nWhen you define a matrix of operating systems, you must set the required runs-on keyword to the operating system of the current job, rather than hard-coding the operating system name. To access the operating system name, you can use the matrix.os context parameter to set runs-on. For more information, see https://help.github.com/en/articles/contexts-and-expression-syntax-for-github-actions.\",\n \"oneOf\": [\n {\n \"type\": \"object\",\n \"patternProperties\": {\n \"^(in|ex)clude$\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#example-including-configurations-in-a-matrix-build\",\n \"oneOf\": [\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n },\n {\n \"type\": \"array\",\n \"items\": {\n \"type\": \"object\",\n \"additionalProperties\": {\n \"$ref\": \"#/definitions/configuration\"\n }\n },\n \"minItems\": 1\n }\n ]\n }\n },\n \"additionalProperties\": {\n \"oneOf\": [\n {\n \"type\": \"array\",\n \"items\": {\n \"$ref\": \"#/definitions/configuration\"\n },\n \"minItems\": 1\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ]\n },\n \"minProperties\": 1\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ]\n },\n \"reusableWorkflowCallJob\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/reusing-workflows#calling-a-reusable-workflow\",\n \"description\": \"Each job must have an id to associate with the job. The key job_id is a string and its value is a map of the job's configuration data. You must replace <job_id> with a string that is unique to the jobs object. The <job_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.\",\n \"type\": \"object\",\n \"properties\": {\n \"name\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname\",\n \"description\": \"The name of the job displayed on GitHub.\",\n \"type\": \"string\"\n },\n \"needs\": {\n \"$ref\": \"#/definitions/jobNeeds\"\n },\n \"permissions\": {\n \"$ref\": \"#/definitions/permissions\"\n },\n \"if\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif\",\n \"description\": \"You can use the if conditional to prevent a job 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.\",\n \"type\": [\"boolean\", \"number\", \"string\"]\n },\n \"uses\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_iduses\",\n \"description\": \"The location and version of a reusable workflow file to run as a job, of the form './{path/to}/{localfile}.yml' or '{owner}/{repo}/{path}/{filename}@{ref}'. {ref} can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security.\",\n \"type\": \"string\",\n \"pattern\": \"^(.+\\\\/)+(.+)\\\\.(ya?ml)(@.+)?$\"\n },\n \"with\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith\",\n \"$ref\": \"#/definitions/env\",\n \"description\": \"A map of inputs that are passed to the called workflow. Any inputs that you pass must match the input specifications defined in the called workflow. Unlike 'jobs.<job_id>.steps[*].with', the inputs you pass with 'jobs.<job_id>.with' are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the inputs context.\"\n },\n \"secrets\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idsecrets\",\n \"description\": \"When a job is used to call a reusable workflow, you can use 'secrets' to provide a map of secrets that are passed to the called workflow. Any secrets that you pass must match the names defined in the called workflow.\",\n \"oneOf\": [\n {\n \"$ref\": \"#/definitions/env\"\n },\n {\n \"type\": \"string\",\n \"enum\": [\"inherit\"]\n }\n ]\n },\n \"strategy\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy\",\n \"description\": \"A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in.\",\n \"type\": \"object\",\n \"properties\": {\n \"matrix\": {\n \"$ref\": \"#/definitions/matrix\"\n },\n \"fail-fast\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast\",\n \"description\": \"When set to true, GitHub cancels all in-progress jobs if any matrix job fails. Default: true\",\n \"type\": [\"boolean\", \"string\"],\n \"default\": true\n },\n \"max-parallel\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel\",\n \"description\": \"The maximum number of jobs that can run simultaneously when using a matrix job strategy. By default, GitHub will maximize the number of jobs run in parallel depending on the available runners on GitHub-hosted virtual machines.\",\n \"type\": [\"number\", \"string\"]\n }\n },\n \"required\": [\"matrix\"],\n \"additionalProperties\": false\n },\n \"concurrency\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idconcurrency\",\n \"description\": \"Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the secrets context. \\nYou can also specify concurrency at the workflow level. \\nWhen a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.\",\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"$ref\": \"#/definitions/concurrency\"\n }\n ]\n }\n },\n \"required\": [\"uses\"],\n \"additionalProperties\": false\n },\n \"normalJob\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id\",\n \"description\": \"Each job must have an id to associate with the job. The key job_id is a string and its value is a map of the job's configuration data. You must replace <job_id> with a string that is unique to the jobs object. The <job_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.\",\n \"type\": \"object\",\n \"properties\": {\n \"name\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname\",\n \"description\": \"The name of the job displayed on GitHub.\",\n \"type\": \"string\"\n },\n \"needs\": {\n \"$ref\": \"#/definitions/jobNeeds\"\n },\n \"snapshot\": {\n \"$ref\": \"#/definitions/snapshot\"\n },\n \"permissions\": {\n \"$ref\": \"#/definitions/permissions\"\n },\n \"runs-on\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on\",\n \"description\": \"The type of machine to run the job on. The machine can be either a GitHub-hosted runner, or a self-hosted runner.\",\n \"anyOf\": [\n {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#github-hosted-runners\",\n \"type\": \"string\"\n },\n {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#self-hosted-runners\",\n \"type\": \"array\",\n \"anyOf\": [\n {\n \"items\": [\n {\n \"type\": \"string\"\n }\n ],\n \"minItems\": 1,\n \"additionalItems\": {\n \"type\": \"string\"\n }\n }\n ]\n },\n {\n \"$comment\": \"https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#choosing-runners-in-a-group\",\n \"type\": \"object\",\n \"properties\": {\n \"group\": {\n \"type\": \"string\"\n },\n \"labels\": {\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"type\": \"array\",\n \"items\": {\n \"type\": \"string\"\n }\n }\n ]\n }\n }\n },\n {\n \"$ref\": \"#/definitions/stringContainingExpressionSyntax\"\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ]\n },\n \"environment\": {\n \"$comment\": \"https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#jobsjob_idenvironment\",\n \"description\": \"The environment that the job references.\",\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"$ref\": \"#/definitions/environment\"\n }\n ]\n },\n \"outputs\": {\n \"$comment\": \"https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idoutputs\",\n \"description\": \"A map of outputs for a job. Job outputs are available to all downstream jobs that depend on this job.\",\n \"type\": \"object\",\n \"additionalProperties\": {\n \"type\": \"string\"\n },\n \"minProperties\": 1\n },\n \"env\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv\",\n \"$ref\": \"#/definitions/env\",\n \"description\": \"A map of environment variables that are available to all steps in the job.\"\n },\n \"defaults\": {\n \"$comment\": \"https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_iddefaults\",\n \"$ref\": \"#/definitions/defaults\",\n \"description\": \"A map of default settings that will apply to all steps in the job.\"\n },\n \"if\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif\",\n \"description\": \"You can use the if conditional to prevent a job 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.\",\n \"type\": [\"boolean\", \"number\", \"string\"]\n },\n \"steps\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps\",\n \"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\",\n \"type\": \"array\",\n \"items\": {\n \"$ref\": \"#/definitions/step\"\n },\n \"minItems\": 1\n },\n \"timeout-minutes\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes\",\n \"description\": \"The maximum number of minutes to let a workflow run before GitHub automatically cancels it. Default: 360\",\n \"oneOf\": [\n {\n \"type\": \"number\"\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ],\n \"default\": 360\n },\n \"strategy\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy\",\n \"description\": \"A strategy creates a build matrix for your jobs. You can define different variations of an environment to run each job in.\",\n \"type\": \"object\",\n \"properties\": {\n \"matrix\": {\n \"$ref\": \"#/definitions/matrix\"\n },\n \"fail-fast\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast\",\n \"description\": \"When set to true, GitHub cancels all in-progress jobs if any matrix job fails. Default: true\",\n \"type\": [\"boolean\", \"string\"],\n \"default\": true\n },\n \"max-parallel\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel\",\n \"description\": \"The maximum number of jobs that can run simultaneously when using a matrix job strategy. By default, GitHub will maximize the number of jobs run in parallel depending on the available runners on GitHub-hosted virtual machines.\",\n \"type\": [\"number\", \"string\"]\n }\n },\n \"required\": [\"matrix\"],\n \"additionalProperties\": false\n },\n \"continue-on-error\": {\n \"$comment\": \"https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error\",\n \"description\": \"Prevents a workflow run from failing when a job fails. Set to true to allow a workflow run to pass when this job fails.\",\n \"oneOf\": [\n {\n \"type\": \"boolean\"\n },\n {\n \"$ref\": \"#/definitions/expressionSyntax\"\n }\n ]\n },\n \"container\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer\",\n \"description\": \"A container to run any steps in a job that don't already specify a container. If you have steps that use both script and container actions, the container actions will run as sibling containers on the same network with the same volume mounts.\\nIf you do not set a container, all steps will run directly on the host specified by runs-on unless a step refers to an action configured to run in a container.\",\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"$ref\": \"#/definitions/container\"\n }\n ]\n },\n \"services\": {\n \"$comment\": \"https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices\",\n \"description\": \"Additional containers to host services for a job in a workflow. These are useful for creating databases or cache services like redis. The runner on the virtual machine will automatically create a network and manage the life cycle of the service containers.\\nWhen you use a service container for a job or your step uses container actions, you don't need to set port information to access the service. Docker automatically exposes all ports between containers on the same network.\\nWhen both the job and the action run in a container, you can directly reference the container by its hostname. The hostname is automatically mapped to the service name.\\nWhen a step does not use a container action, you must access the service using localhost and bind the ports.\",\n \"type\": \"object\",\n \"additionalProperties\": {\n \"$ref\": \"#/definitions/container\"\n }\n },\n \"concurrency\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idconcurrency\",\n \"description\": \"Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the secrets context. \\nYou can also specify concurrency at the workflow level. \\nWhen a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.\",\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"$ref\": \"#/definitions/concurrency\"\n }\n ]\n }\n },\n \"required\": [\"runs-on\"],\n \"additionalProperties\": false\n },\n \"workflowDispatchInput\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_id\",\n \"description\": \"A string identifier to associate with the input. The value of <input_id> is a map of the input's metadata. The <input_id> must be a unique identifier within the inputs object. The <input_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.\",\n \"type\": \"object\",\n \"properties\": {\n \"description\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_iddescription\",\n \"description\": \"A string description of the input parameter.\",\n \"type\": \"string\"\n },\n \"deprecationMessage\": {\n \"description\": \"A string shown to users using the deprecated input.\",\n \"type\": \"string\"\n },\n \"required\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_idrequired\",\n \"description\": \"A boolean to indicate whether the action requires the input parameter. Set to true when the parameter is required.\",\n \"type\": \"boolean\"\n },\n \"default\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_iddefault\",\n \"description\": \"A string representing the default value. The default value is used when an input parameter isn't specified in a workflow file.\"\n },\n \"type\": {\n \"$comment\": \"https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputsinput_idtype\",\n \"description\": \"A string representing the type of the input.\",\n \"type\": \"string\",\n \"enum\": [\"string\", \"choice\", \"boolean\", \"number\", \"environment\"]\n },\n \"options\": {\n \"$comment\": \"https://github.blog/changelog/2021-11-10-github-actions-input-types-for-manual-workflows\",\n \"description\": \"The options of the dropdown list, if the type is a choice.\",\n \"type\": \"array\",\n \"items\": {\n \"type\": \"string\"\n },\n \"minItems\": 1\n }\n },\n \"allOf\": [\n {\n \"if\": {\n \"properties\": {\n \"type\": {\n \"const\": \"string\"\n }\n },\n \"required\": [\"type\"]\n },\n \"then\": {\n \"properties\": {\n \"default\": {\n \"type\": \"string\"\n }\n }\n }\n },\n {\n \"if\": {\n \"properties\": {\n \"type\": {\n \"const\": \"boolean\"\n }\n },\n \"required\": [\"type\"]\n },\n \"then\": {\n \"properties\": {\n \"default\": {\n \"type\": \"boolean\"\n }\n }\n }\n },\n {\n \"if\": {\n \"properties\": {\n \"type\": {\n \"const\": \"number\"\n }\n },\n \"required\": [\"type\"]\n },\n \"then\": {\n \"properties\": {\n \"default\": {\n \"type\": \"number\"\n }\n }\n }\n },\n {\n \"if\": {\n \"properties\": {\n \"type\": {\n \"const\": \"environment\"\n }\n },\n \"required\": [\"type\"]\n },\n \"then\": {\n \"properties\": {\n \"default\": {\n \"type\": \"string\"\n }\n }\n }\n },\n {\n \"if\": {\n \"properties\": {\n \"type\": {\n \"const\": \"choice\"\n }\n },\n \"required\": [\"type\"]\n },\n \"then\": {\n \"required\": [\"options\"]\n }\n }\n ],\n \"additionalProperties\": false\n }\n },\n \"properties\": {\n \"name\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#name\",\n \"description\": \"The name of your workflow. GitHub displays the names of your workflows on your repository's actions page. If you omit this field, GitHub sets the name to the workflow's filename.\",\n \"type\": \"string\"\n },\n \"on\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on\",\n \"description\": \"The name of the GitHub event that triggers the workflow. You can provide a single event string, array of events, array of event types, or an event configuration map that schedules a workflow or restricts the execution of a workflow to specific files, tags, or branch changes. For a list of available events, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows.\",\n \"oneOf\": [\n {\n \"$ref\": \"#/definitions/event\"\n },\n {\n \"type\": \"array\",\n \"items\": {\n \"$ref\": \"#/definitions/event\"\n },\n \"minItems\": 1\n },\n {\n \"type\": \"object\",\n \"properties\": {\n \"branch_protection_rule\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#branch_protection_rule\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the branch_protection_rule event occurs. More than one activity type triggers this event.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"edited\", \"deleted\"]\n }\n }\n },\n \"check_run\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#check-run-event-check_run\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the check_run event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/checks/runs.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"rerequested\", \"completed\", \"requested_action\"]\n },\n \"default\": [\"created\", \"rerequested\", \"completed\", \"requested_action\"]\n }\n }\n },\n \"check_suite\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#check-suite-event-check_suite\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the check_suite event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/checks/suites/.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"completed\", \"requested\", \"rerequested\"]\n },\n \"default\": [\"completed\", \"requested\", \"rerequested\"]\n }\n }\n },\n \"create\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#create-event-create\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime someone creates a branch or tag, which triggers the create event. For information about the REST API, see https://developer.github.com/v3/git/refs/#create-a-reference.\"\n },\n \"delete\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#delete-event-delete\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime someone deletes a branch or tag, which triggers the delete event. For information about the REST API, see https://developer.github.com/v3/git/refs/#delete-a-reference.\"\n },\n \"deployment\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#deployment-event-deployment\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime someone creates a deployment, which triggers the deployment event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see https://developer.github.com/v3/repos/deployments/.\"\n },\n \"deployment_status\": {\n \"$comment\": \"https://docs.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime a third party provides a deployment status, which triggers the deployment_status event. Deployments created with a commit SHA may not have a Git ref. For information about the REST API, see https://developer.github.com/v3/repos/deployments/#create-a-deployment-status.\"\n },\n \"discussion\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/events-that-trigger-workflows#discussion\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the discussion event occurs. More than one activity type triggers this event. For information about the GraphQL API, see https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\n \"created\",\n \"edited\",\n \"deleted\",\n \"transferred\",\n \"pinned\",\n \"unpinned\",\n \"labeled\",\n \"unlabeled\",\n \"locked\",\n \"unlocked\",\n \"category_changed\",\n \"answered\",\n \"unanswered\"\n ]\n },\n \"default\": [\n \"created\",\n \"edited\",\n \"deleted\",\n \"transferred\",\n \"pinned\",\n \"unpinned\",\n \"labeled\",\n \"unlabeled\",\n \"locked\",\n \"unlocked\",\n \"category_changed\",\n \"answered\",\n \"unanswered\"\n ]\n }\n }\n },\n \"discussion_comment\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/events-that-trigger-workflows#discussion_comment\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the discussion_comment event occurs. More than one activity type triggers this event. For information about the GraphQL API, see https://docs.github.com/en/graphql/guides/using-the-graphql-api-for-discussions\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"edited\", \"deleted\"]\n }\n }\n },\n \"fork\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#fork-event-fork\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime when someone forks a repository, which triggers the fork event. For information about the REST API, see https://developer.github.com/v3/repos/forks/#create-a-fork.\"\n },\n \"gollum\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#gollum-event-gollum\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow when someone creates or updates a Wiki page, which triggers the gollum event.\"\n },\n \"issue_comment\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#issue-comment-event-issue_comment\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the issue_comment event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues/comments/.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"edited\", \"deleted\"]\n }\n }\n },\n \"issues\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#issues-event-issues\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the issues event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\n \"opened\",\n \"edited\",\n \"deleted\",\n \"transferred\",\n \"pinned\",\n \"unpinned\",\n \"closed\",\n \"reopened\",\n \"assigned\",\n \"unassigned\",\n \"labeled\",\n \"unlabeled\",\n \"locked\",\n \"unlocked\",\n \"milestoned\",\n \"demilestoned\"\n ]\n },\n \"default\": [\n \"opened\",\n \"edited\",\n \"deleted\",\n \"transferred\",\n \"pinned\",\n \"unpinned\",\n \"closed\",\n \"reopened\",\n \"assigned\",\n \"unassigned\",\n \"labeled\",\n \"unlabeled\",\n \"locked\",\n \"unlocked\",\n \"milestoned\",\n \"demilestoned\"\n ]\n }\n }\n },\n \"label\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#label-event-label\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the label event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues/labels/.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"edited\", \"deleted\"]\n }\n }\n },\n \"merge_group\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#merge_group\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow when a pull request is added to a merge queue, which adds the pull request to a merge group. For information about the merge queue, see https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue .\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"checks_requested\"]\n },\n \"default\": [\"checks_requested\"]\n }\n }\n },\n \"milestone\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#milestone-event-milestone\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the milestone event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/issues/milestones/.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"closed\", \"opened\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"closed\", \"opened\", \"edited\", \"deleted\"]\n }\n }\n },\n \"page_build\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#page-build-event-page_build\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime someone pushes to a GitHub Pages-enabled branch, which triggers the page_build event. For information about the REST API, see https://developer.github.com/v3/repos/pages/.\"\n },\n \"project\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#project-event-project\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the project event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/projects/.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"updated\", \"closed\", \"reopened\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"updated\", \"closed\", \"reopened\", \"edited\", \"deleted\"]\n }\n }\n },\n \"project_card\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#project-card-event-project_card\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the project_card event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/projects/cards.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"moved\", \"converted\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"moved\", \"converted\", \"edited\", \"deleted\"]\n }\n }\n },\n \"project_column\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#project-column-event-project_column\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the project_column event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/projects/columns.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"updated\", \"moved\", \"deleted\"]\n },\n \"default\": [\"created\", \"updated\", \"moved\", \"deleted\"]\n }\n }\n },\n \"public\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#public-event-public\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime someone makes a private repository public, which triggers the public event. For information about the REST API, see https://developer.github.com/v3/repos/#edit.\"\n },\n \"pull_request\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#pull-request-event-pull_request\",\n \"description\": \"Runs your workflow anytime the pull_request event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/pulls.\\nNote: Workflows do not run on private base repositories when you open a pull request from a forked repository.\\nWhen you create a pull request from a forked repository to the base repository, GitHub sends the pull_request event to the base repository and no pull request events occur on the forked repository.\\nWorkflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.\\nThe permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the GITHUB_TOKEN, see https://help.github.com/en/articles/virtual-environments-for-github-actions.\",\n \"oneOf\": [\n {\n \"type\": \"null\"\n },\n {\n \"allOf\": [\n {\n \"type\": \"object\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\n \"assigned\",\n \"unassigned\",\n \"labeled\",\n \"unlabeled\",\n \"opened\",\n \"edited\",\n \"closed\",\n \"reopened\",\n \"synchronize\",\n \"converted_to_draft\",\n \"ready_for_review\",\n \"locked\",\n \"unlocked\",\n \"milestoned\",\n \"demilestoned\",\n \"review_requested\",\n \"review_request_removed\",\n \"auto_merge_enabled\",\n \"auto_merge_disabled\",\n \"enqueued\",\n \"dequeued\"\n ]\n },\n \"default\": [\"opened\", \"synchronize\", \"reopened\"]\n },\n \"branches\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"branches-ignore\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"tags\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"tags-ignore\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"paths\": {\n \"$ref\": \"#/definitions/path\"\n },\n \"paths-ignore\": {\n \"$ref\": \"#/definitions/path\"\n }\n },\n \"additionalProperties\": false\n },\n {\n \"not\": {\n \"required\": [\"branches\", \"branches-ignore\"]\n }\n },\n {\n \"not\": {\n \"required\": [\"tags\", \"tags-ignore\"]\n }\n },\n {\n \"not\": {\n \"required\": [\"paths\", \"paths-ignore\"]\n }\n }\n ]\n }\n ]\n },\n \"pull_request_review\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#pull-request-review-event-pull_request_review\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the pull_request_review event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/pulls/reviews.\\nNote: Workflows do not run on private base repositories when you open a pull request from a forked repository.\\nWhen you create a pull request from a forked repository to the base repository, GitHub sends the pull_request event to the base repository and no pull request events occur on the forked repository.\\nWorkflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.\\nThe permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the GITHUB_TOKEN, see https://help.github.com/en/articles/virtual-environments-for-github-actions.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"submitted\", \"edited\", \"dismissed\"]\n },\n \"default\": [\"submitted\", \"edited\", \"dismissed\"]\n }\n }\n },\n \"pull_request_review_comment\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#pull-request-review-comment-event-pull_request_review_comment\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime a comment on a pull request's unified diff is modified, which triggers the pull_request_review_comment event. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/pulls/comments.\\nNote: Workflows do not run on private base repositories when you open a pull request from a forked repository.\\nWhen you create a pull request from a forked repository to the base repository, GitHub sends the pull_request event to the base repository and no pull request events occur on the forked repository.\\nWorkflows don't run on forked repositories by default. You must enable GitHub Actions in the Actions tab of the forked repository.\\nThe permissions for the GITHUB_TOKEN in forked repositories is read-only. For more information about the GITHUB_TOKEN, see https://help.github.com/en/articles/virtual-environments-for-github-actions.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"created\", \"edited\", \"deleted\"]\n },\n \"default\": [\"created\", \"edited\", \"deleted\"]\n }\n }\n },\n \"pull_request_target\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request_target\",\n \"description\": \"This event is similar to pull_request, except that it runs in the context of the base repository of the pull request, rather than in the merge commit. This means that you can more safely make your secrets available to the workflows triggered by the pull request, because only workflows defined in the commit on the base repository are run. For example, this event allows you to create workflows that label and comment on pull requests, based on the contents of the event payload.\",\n \"oneOf\": [\n {\n \"type\": \"null\"\n },\n {\n \"allOf\": [\n {\n \"type\": \"object\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\n \"assigned\",\n \"unassigned\",\n \"labeled\",\n \"unlabeled\",\n \"opened\",\n \"edited\",\n \"closed\",\n \"reopened\",\n \"synchronize\",\n \"converted_to_draft\",\n \"ready_for_review\",\n \"locked\",\n \"unlocked\",\n \"review_requested\",\n \"review_request_removed\",\n \"auto_merge_enabled\",\n \"auto_merge_disabled\"\n ]\n },\n \"default\": [\"opened\", \"synchronize\", \"reopened\"]\n },\n \"branches\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"branches-ignore\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"tags\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"tags-ignore\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"paths\": {\n \"$ref\": \"#/definitions/path\"\n },\n \"paths-ignore\": {\n \"$ref\": \"#/definitions/path\"\n }\n },\n \"additionalProperties\": false\n },\n {\n \"not\": {\n \"required\": [\"branches\", \"branches-ignore\"]\n }\n },\n {\n \"not\": {\n \"required\": [\"tags\", \"tags-ignore\"]\n }\n },\n {\n \"not\": {\n \"required\": [\"paths\", \"paths-ignore\"]\n }\n }\n ]\n }\n ]\n },\n \"push\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#push-event-push\",\n \"description\": \"Runs your workflow when someone pushes to a repository branch, which triggers the push event.\\nNote: The webhook payload available to GitHub Actions does not include the added, removed, and modified attributes in the commit object. You can retrieve the full commit object using the REST API. For more information, see https://developer.github.com/v3/repos/commits/#get-a-single-commit.\",\n \"oneOf\": [\n {\n \"type\": \"null\"\n },\n {\n \"allOf\": [\n {\n \"type\": \"object\",\n \"properties\": {\n \"branches\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"branches-ignore\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"tags\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"tags-ignore\": {\n \"$ref\": \"#/definitions/branch\"\n },\n \"paths\": {\n \"$ref\": \"#/definitions/path\"\n },\n \"paths-ignore\": {\n \"$ref\": \"#/definitions/path\"\n }\n },\n \"additionalProperties\": false\n },\n {\n \"not\": {\n \"required\": [\"branches\", \"branches-ignore\"]\n }\n },\n {\n \"not\": {\n \"required\": [\"tags\", \"tags-ignore\"]\n }\n },\n {\n \"not\": {\n \"required\": [\"paths\", \"paths-ignore\"]\n }\n }\n ]\n }\n ]\n },\n \"registry_package\": {\n \"$comment\": \"https://help.github.com/en/actions/reference/events-that-trigger-workflows#registry-package-event-registry_package\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime a package is published or updated. For more information, see https://help.github.com/en/github/managing-packages-with-github-packages.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"published\", \"updated\"]\n },\n \"default\": [\"published\", \"updated\"]\n }\n }\n },\n \"release\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#release-event-release\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the release event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/repos/releases/ in the GitHub Developer documentation.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\n \"published\",\n \"unpublished\",\n \"created\",\n \"edited\",\n \"deleted\",\n \"prereleased\",\n \"released\"\n ]\n },\n \"default\": [\n \"published\",\n \"unpublished\",\n \"created\",\n \"edited\",\n \"deleted\",\n \"prereleased\",\n \"released\"\n ]\n }\n }\n },\n \"status\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#status-event-status\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the status of a Git commit changes, which triggers the status event. For information about the REST API, see https://developer.github.com/v3/repos/statuses/.\"\n },\n \"watch\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#watch-event-watch\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"Runs your workflow anytime the watch event occurs. More than one activity type triggers this event. For information about the REST API, see https://developer.github.com/v3/activity/starring/.\"\n },\n \"workflow_call\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/events-that-trigger-workflows#workflow_call\",\n \"description\": \"Allows workflows to be reused by other workflows.\",\n \"properties\": {\n \"inputs\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs\",\n \"description\": \"When using the workflow_call keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow.\",\n \"type\": \"object\",\n \"patternProperties\": {\n \"^[_a-zA-Z][a-zA-Z0-9_-]*$\": {\n \"$comment\": \"https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id\",\n \"description\": \"A string identifier to associate with the input. The value of <input_id> is a map of the input's metadata. The <input_id> must be a unique identifier within the inputs object. The <input_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.\",\n \"type\": \"object\",\n \"properties\": {\n \"description\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_iddescription\",\n \"description\": \"A string description of the input parameter.\",\n \"type\": \"string\"\n },\n \"required\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_idrequired\",\n \"description\": \"A boolean to indicate whether the action requires the input parameter. Set to true when the parameter is required.\",\n \"type\": \"boolean\"\n },\n \"type\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_callinput_idtype\",\n \"description\": \"Required if input is defined for the on.workflow_call keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: boolean, number, or string.\",\n \"type\": \"string\",\n \"enum\": [\"boolean\", \"number\", \"string\"]\n },\n \"default\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputsinput_iddefault\",\n \"description\": \"The default value is used when an input parameter isn't specified in a workflow file.\",\n \"type\": [\"boolean\", \"number\", \"string\"]\n }\n },\n \"required\": [\"type\"],\n \"additionalProperties\": false\n }\n },\n \"additionalProperties\": false\n },\n \"outputs\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#onworkflow_calloutputs\",\n \"description\": \"When using the workflow_call keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow.\",\n \"type\": \"object\",\n \"patternProperties\": {\n \"^[_a-zA-Z][a-zA-Z0-9_-]*$\": {\n \"$comment\": \"https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#outputsoutput_id\",\n \"description\": \"A string identifier to associate with the output. The value of <output_id> is a map of the output's metadata. The <output_id> must be a unique identifier within the outputs object. The <output_id> must start with a letter or _ and contain only alphanumeric characters, -, or _.\",\n \"type\": \"object\",\n \"properties\": {\n \"description\": {\n \"$comment\": \"https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#outputsoutput_iddescription\",\n \"description\": \"A string description of the output parameter.\",\n \"type\": \"string\"\n },\n \"value\": {\n \"$comment\": \"https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#outputsoutput_idvalue\",\n \"description\": \"The value that the output parameter will be mapped to. You can set this to a string or an expression with context. For example, you can use the steps context to set the value of an output to the output value of a step.\",\n \"type\": \"string\"\n }\n },\n \"required\": [\"value\"],\n \"additionalProperties\": false\n }\n },\n \"additionalProperties\": false\n },\n \"secrets\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_callsecrets\",\n \"description\": \"A map of the secrets that can be used in the called workflow. Within the called workflow, you can use the secrets context to refer to a secret.\",\n \"patternProperties\": {\n \"^[_a-zA-Z][a-zA-Z0-9_-]*$\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_callsecretssecret_id\",\n \"description\": \"A string identifier to associate with the secret.\",\n \"properties\": {\n \"description\": {\n \"description\": \"A string description of the secret parameter.\",\n \"type\": \"string\"\n },\n \"required\": {\n \"$comment\": \"https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_callsecretssecret_idrequired\",\n \"description\": \"A boolean specifying whether the secret must be supplied.\",\n \"type\": \"boolean\"\n }\n },\n \"additionalProperties\": false\n }\n },\n \"additionalProperties\": false\n }\n }\n },\n \"workflow_dispatch\": {\n \"$comment\": \"https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/\",\n \"description\": \"You can now create workflows that are manually triggered with the new workflow_dispatch event. You will then see a 'Run workflow' button on the Actions tab, enabling you to easily trigger a run.\",\n \"properties\": {\n \"inputs\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs\",\n \"description\": \"Input parameters allow you to specify data that the action expects to use during runtime. GitHub stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.\",\n \"type\": \"object\",\n \"patternProperties\": {\n \"^[_a-zA-Z][a-zA-Z0-9_-]*$\": {\n \"$ref\": \"#/definitions/workflowDispatchInput\"\n }\n },\n \"additionalProperties\": false\n }\n },\n \"additionalProperties\": false\n },\n \"workflow_run\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_run\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"This event occurs when a workflow run is requested or completed, and allows you to execute a workflow based on the finished result of another workflow. For example, if your pull_request workflow generates build artifacts, you can create a new workflow that uses workflow_run to analyze the results and add a comment to the original pull request.\",\n \"properties\": {\n \"types\": {\n \"$ref\": \"#/definitions/types\",\n \"items\": {\n \"type\": \"string\",\n \"enum\": [\"requested\", \"completed\", \"in_progress\"]\n },\n \"default\": [\"requested\", \"completed\"]\n },\n \"workflows\": {\n \"type\": \"array\",\n \"items\": {\n \"type\": \"string\"\n },\n \"minItems\": 1\n }\n },\n \"patternProperties\": {\n \"^branches(-ignore)?$\": {}\n }\n },\n \"repository_dispatch\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#external-events-repository_dispatch\",\n \"$ref\": \"#/definitions/eventObject\",\n \"description\": \"You can use the GitHub API to trigger a webhook event called repository_dispatch when you want to trigger a workflow for activity that happens outside of GitHub. For more information, see https://developer.github.com/v3/repos/#create-a-repository-dispatch-event.\\nTo trigger the custom repository_dispatch webhook event, you must send a POST request to a GitHub API endpoint and provide an event_type name to describe the activity type. To trigger a workflow run, you must also configure your workflow to use the repository_dispatch event.\"\n },\n \"schedule\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events-schedule\",\n \"description\": \"You can schedule a workflow to run at specific UTC times using POSIX cron syntax (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Scheduled workflows run on the latest commit on the default or base branch. The shortest interval you can run scheduled workflows is once every 5 minutes.\\nNote: GitHub Actions does not support the non-standard syntax @yearly, @monthly, @weekly, @daily, @hourly, and @reboot.\\nYou can use crontab guru (https://crontab.guru/). to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of crontab guru examples (https://crontab.guru/examples.html).\",\n \"type\": \"array\",\n \"items\": {\n \"type\": \"object\",\n \"properties\": {\n \"cron\": {\n \"type\": \"string\"\n }\n },\n \"additionalProperties\": false\n },\n \"minItems\": 1\n }\n },\n \"additionalProperties\": false\n }\n ]\n },\n \"env\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env\",\n \"$ref\": \"#/definitions/env\",\n \"description\": \"A map of environment variables that are available to all jobs and steps in the workflow.\"\n },\n \"defaults\": {\n \"$comment\": \"https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#defaults\",\n \"$ref\": \"#/definitions/defaults\",\n \"description\": \"A map of default settings that will apply to all jobs in the workflow.\"\n },\n \"concurrency\": {\n \"$comment\": \"https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#concurrency\",\n \"description\": \"Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can use any context except for the secrets context. \\nYou can also specify concurrency at the workflow level. \\nWhen a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be pending. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify cancel-in-progress: true.\",\n \"oneOf\": [\n {\n \"type\": \"string\"\n },\n {\n \"$ref\": \"#/definitions/concurrency\"\n }\n ]\n },\n \"jobs\": {\n \"$comment\": \"https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs\",\n \"description\": \"A workflow run is made up of one or more jobs. Jobs run in parallel by default. To run jobs sequentially, you can define dependencies on other jobs using the jobs.<job_id>.needs keyword.\\nEach job runs in a fresh instance of the virtual environment specified by runs-on.\\nYou can run an unlimited number of jobs as long as you are within the workflow usage limits. For more information, see https://help.github.com/en/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#usage-limits.\",\n \"type\": \"object\",\n \"patternProperties\": {\n \"^[_a-zA-Z][a-zA-Z0-9_-]*$\": {\n \"oneOf\": [\n {\n \"$ref\": \"#/definitions/normalJob\"\n },\n {\n \"$ref\": \"#/definitions/reusableWorkflowCallJob\"\n }\n ]\n }\n },\n \"minProperties\": 1,\n \"additionalProperties\": false\n },\n \"run-name\": {\n \"$comment\": \"https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#run-name\",\n \"description\": \"The name for workflow runs generated from the workflow. GitHub displays the workflow run name in the list of workflow runs on your repository's 'Actions' tab.\",\n \"type\": \"string\"\n },\n \"permissions\": {\n \"$ref\": \"#/definitions/permissions\"\n },\n \"enable-email-notifications\": {\n \"type\": \"boolean\",\n \"description\": \"Send an email notification when a workflow run fails or recovers from a failure. (Forgejo-specific)\"\n }\n },\n \"required\": [\"on\", \"jobs\"],\n \"type\": \"object\"\n}\n";
8939
8931
  const existingSchema = ctx.read(SCHEMA_LOCAL_PATH);
8940
8932
  if (existingSchema !== void 0 && contentEqual(SCHEMA_LOCAL_PATH, existingSchema, schemaContent)) results.push({
8941
8933
  filePath: SCHEMA_LOCAL_PATH,
@@ -8947,7 +8939,7 @@ async function generateVscodeSettings(ctx) {
8947
8939
  results.push({
8948
8940
  filePath: SCHEMA_LOCAL_PATH,
8949
8941
  action: existingSchema ? "updated" : "created",
8950
- description: "Copied Forgejo workflow schema from @bensandee/config"
8942
+ description: "Wrote the Forgejo workflow schema"
8951
8943
  });
8952
8944
  }
8953
8945
  results.push(writeSchemaToSettings(ctx));
@@ -9291,7 +9283,15 @@ const AGENT_RULES_MID = [
9291
9283
  "- Write text in any language; letters, accents and other scripts are fine. Keep out what `chars:check` denies: LLM-tell punctuation (curly quotes, ellipsis, en and em dashes, arrows, box-drawing, status glyphs) and invisible or deceptive characters (bidi controls, zero-width and tag characters, odd spaces). Write `...`, `-`/`--`, straight quotes, `->` and `-`/`|`/`+` instead. Where a denied character must survive to output, escape it for its context: `\\uXXXX` in a JS/TS/Kotlin/Java string, char or regex; `&#xXXXX;` in JSX or XML; a spliced `${'\\uXXXX'}` in a Kotlin raw string. `pnpm exec bst chars:check --fix` applies the safe rewrites (`--fix-ambiguous` for em dashes and status glyphs) and flags the rest.",
9292
9284
  "- Write in plain language, per ISO 24495-1 -- every word you produce, code comments and commit bodies included."
9293
9285
  ];
9294
- const TS_EXTENSIONLESS_RULE = "- Prefer extensionless imports; if an extension is required, use `.ts` over `.js`.";
9286
+ const TS_IMPORT_RULE_BUNDLER = "- Prefer extensionless imports; if an extension is required, use `.ts` over `.js`.";
9287
+ const TS_IMPORT_RULE_ALWAYS_TS = "- Relative imports always carry the `.ts` extension.";
9288
+ const TS_IMPORT_RULE_CONDITIONAL = "- Relative imports carry `.ts` with no build step or `nodenext` resolution; otherwise prefer extensionless.";
9289
+ function importRule(config) {
9290
+ if (config.structure === "monorepo") return TS_IMPORT_RULE_CONDITIONAL;
9291
+ if (config.builder === "none" || config.projectType === "node") return TS_IMPORT_RULE_ALWAYS_TS;
9292
+ if (config.builder === "custom") return TS_IMPORT_RULE_CONDITIONAL;
9293
+ return TS_IMPORT_RULE_BUNDLER;
9294
+ }
9295
9295
  const CHANGESETS_RULE = "- A user-facing change owes a changeset in `.changeset/`, written with the change: `patch` for a fix, `minor` for a feature, naming every package it affects. One file per smallest unit of work.";
9296
9296
  const WORK_STATUS_RULE = "- Before starting or resuming work, run `pnpm exec bst work:status`.";
9297
9297
  const WORK_START_RULE = "- Before starting or resuming work, run `pnpm exec bst work:start <n>`.";
@@ -9772,7 +9772,7 @@ function agentRulesBody(config, guides, packageJson, agentWorked) {
9772
9772
  const lines = [...AGENT_RULES_HEAD];
9773
9773
  if (config.stack === "typescript") lines.push(TS_TYPECAST_RULE);
9774
9774
  lines.push(...AGENT_RULES_MID);
9775
- if (config.stack === "typescript") lines.push(TS_EXTENSIONLESS_RULE);
9775
+ if (config.stack === "typescript") lines.push(importRule(config));
9776
9776
  if (config.releaseStrategy === "changesets") lines.push(CHANGESETS_RULE);
9777
9777
  const tail = agentRulesTail(agentWorked).map((line) => line === FIND_COMMAND_RULE ? findCommandRule(packageJson) : line);
9778
9778
  lines.push(...tail, "", guideIndex(guides));
@@ -10079,7 +10079,7 @@ function reportFailures(failed, command) {
10079
10079
  function generateMigratePrompt(results, config, detected) {
10080
10080
  const sections = [];
10081
10081
  const timestamp = (/* @__PURE__ */ new Date()).toISOString();
10082
- sections.push(`# Migration Prompt\n\n_Generated by \`@bensandee/tooling@0.93.0 repo:sync\` on ${timestamp}_\n`);
10082
+ sections.push(`# Migration Prompt\n\n_Generated by \`@bensandee/tooling@0.93.1 repo:sync\` on ${timestamp}_\n`);
10083
10083
  const changed = results.filter((r) => r.action === "created" || r.action === "updated" || r.action === "archived");
10084
10084
  if (changed.length > 0) {
10085
10085
  const items = changed.map((r) => {
@@ -16088,6 +16088,27 @@ const OUTPUT_GLYPH_OFFENDERS = [
16088
16088
  char: "▶",
16089
16089
  replacement: ">"
16090
16090
  },
16091
+ {
16092
+ codepoint: "U+25BA",
16093
+ name: "BLACK RIGHT-POINTING POINTER",
16094
+ tier: 2,
16095
+ char: "►",
16096
+ replacement: ">"
16097
+ },
16098
+ {
16099
+ codepoint: "U+25C4",
16100
+ name: "BLACK LEFT-POINTING POINTER",
16101
+ tier: 2,
16102
+ char: "◄",
16103
+ replacement: "<"
16104
+ },
16105
+ {
16106
+ codepoint: "U+25C0",
16107
+ name: "BLACK LEFT-POINTING TRIANGLE",
16108
+ tier: 2,
16109
+ char: "◀",
16110
+ replacement: "<"
16111
+ },
16091
16112
  {
16092
16113
  codepoint: "U+0394",
16093
16114
  name: "GREEK CAPITAL LETTER DELTA",
@@ -27870,7 +27891,7 @@ async function runCli(config) {
27870
27891
  //#region src/cli-main.ts
27871
27892
  setLogLevel(resolveLogLevel({}));
27872
27893
  setForgejoLogger(log$1);
27873
- const displayVersion = "0.93.0";
27894
+ const displayVersion = "0.93.1";
27874
27895
  const bstSubCommands = {
27875
27896
  "repo:sync": syncCommand,
27876
27897
  "checks:run": runChecksCommand,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bensandee/tooling",
3
- "version": "0.93.0",
3
+ "version": "0.93.1",
4
4
  "description": "CLI tool to bootstrap and maintain standardized TypeScript project tooling",
5
5
  "license": "MIT",
6
6
  "repository": {