nx 22.0.0-beta.2 → 22.0.0-beta.4

package/migrations.json

@@ -88,6 +88,11 @@
       "version": "21.1.0-beta.2",
       "description": "Adds **/nx-rules.mdc and **/nx.instructions.md to .gitignore if not present",
       "implementation": "./src/migrations/update-21-1-0/add-gitignore-entry"
+    },
+    "22-0-0-release-version-config-changes": {
+      "version": "22.0.0-beta.1",
+      "description": "Updates release version config based on the breaking changes in Nx v22",
+      "implementation": "./src/migrations/update-22-0-0/release-version-config-changes"
     }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nx",
-  "version": "22.0.0-beta.2",
+  "version": "22.0.0-beta.4",
   "private": false,
   "description": "The core Nx plugin contains the core functionality of Nx like the project graph, nx commands and task orchestration.",
   "repository": {
@@ -38,7 +38,7 @@
     "@yarnpkg/lockfile": "^1.1.0",
     "@yarnpkg/parsers": "3.0.2",
     "@zkochan/js-yaml": "0.0.7",
-    "axios": "^1.8.3",
+    "axios": "^1.12.0",
     "chalk": "^4.1.0",
     "cli-cursor": "3.1.0",
     "cli-spinners": "2.6.1",
@@ -83,16 +83,16 @@
     }
   },
   "optionalDependencies": {
-    "@nx/nx-darwin-arm64": "22.0.0-beta.2",
-    "@nx/nx-darwin-x64": "22.0.0-beta.2",
-    "@nx/nx-freebsd-x64": "22.0.0-beta.2",
-    "@nx/nx-linux-arm-gnueabihf": "22.0.0-beta.2",
-    "@nx/nx-linux-arm64-gnu": "22.0.0-beta.2",
-    "@nx/nx-linux-arm64-musl": "22.0.0-beta.2",
-    "@nx/nx-linux-x64-gnu": "22.0.0-beta.2",
-    "@nx/nx-linux-x64-musl": "22.0.0-beta.2",
-    "@nx/nx-win32-arm64-msvc": "22.0.0-beta.2",
-    "@nx/nx-win32-x64-msvc": "22.0.0-beta.2"
+    "@nx/nx-darwin-arm64": "22.0.0-beta.4",
+    "@nx/nx-darwin-x64": "22.0.0-beta.4",
+    "@nx/nx-freebsd-x64": "22.0.0-beta.4",
+    "@nx/nx-linux-arm-gnueabihf": "22.0.0-beta.4",
+    "@nx/nx-linux-arm64-gnu": "22.0.0-beta.4",
+    "@nx/nx-linux-arm64-musl": "22.0.0-beta.4",
+    "@nx/nx-linux-x64-gnu": "22.0.0-beta.4",
+    "@nx/nx-linux-x64-musl": "22.0.0-beta.4",
+    "@nx/nx-win32-arm64-msvc": "22.0.0-beta.4",
+    "@nx/nx-win32-x64-msvc": "22.0.0-beta.4"
   },
   "nx-migrations": {
     "migrations": "./migrations.json",

package/project.json

@@ -67,7 +67,8 @@
                 "production",
                 "^production",
                 {
-                    "dependentTasksOutputFiles": "**/*.node"
+                    "dependentTasksOutputFiles": "**/*.node",
+                    "transitive": true
                 }
             ],
             "executor": "nx:run-commands",

package/schemas/nx-schema.json

@@ -87,7 +87,14 @@
           "default": true
         },
         "autoExit": {
-          "oneOf": [{ "type": "boolean" }, { "type": "number" }],
+          "oneOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "number"
+            }
+          ],
           "description": "Whether to exit the TUI automatically after all tasks finish. If set to `true`, the TUI will exit immediately. If set to `false` the TUI will not automatically exit. If set to a number, an interruptible countdown popup will be shown for that many seconds before the TUI exits.",
           "default": 3
         }
@@ -211,6 +218,11 @@
                 "type": "boolean",
                 "description": "Whether to require semver to be used for the release tag pattern. If set to false, the release tag pattern will not be checked for semver compliance."
               },
+              "releaseTagPatternPreferDockerVersion": {
+                "type": ["boolean", "string"],
+                "enum": [true, false, "both"],
+                "description": "Controls how docker versions are used relative to semver versions when creating git tags and changelog entries. Set to true to use only the docker version, false to use only the semver version, or 'both' to create tags and changelog entries for both docker and semver versions. By default, this is set to true when docker configuration is present, and false otherwise."
+              },
               "releaseTagPatternStrictPreid": {
                 "$ref": "#/definitions/NxReleaseReleaseTagPatternStrictPreidConfiguration"
               },
@@ -319,6 +331,11 @@
           "type": "boolean",
           "description": "Whether to require semver to be used for the release tag pattern. If set to false, the release tag pattern will not be checked for semver compliance."
         },
+        "releaseTagPatternPreferDockerVersion": {
+          "type": ["boolean", "string"],
+          "enum": [true, false, "both"],
+          "description": "Controls how docker versions are used relative to semver versions when creating git tags and changelog entries. Set to true to use only the docker version, false to use only the semver version, or 'both' to create tags and changelog entries for both docker and semver versions. By default, this is set to true when docker configuration is present, and false otherwise."
+        },
         "releaseTagPatternStrictPreid": {
           "$ref": "#/definitions/NxReleaseReleaseTagPatternStrictPreidConfiguration"
         },
@@ -752,181 +769,240 @@
     },
     "NxReleaseVersionConfiguration": {
       "type": "object",
-      "$comment": "The configuration for versioning is dynamic depending on the value of the useLegacyVersioning property. Through trial and error the best in editor DX seems to come from having the if/else at the top level and explicitly include all possible properties and apply additionalProperties false in each case.",
       "description": "Configuration for the versioning phase of releases.",
-      "if": {
-        "$comment": "When using the latest versioning implementation a lot of configuration has been able to move directly onto the version property.",
-        "properties": {
-          "useLegacyVersioning": {
-            "const": false
-          }
-        }
-      },
-      "then": {
-        "additionalProperties": false,
-        "properties": {
-          "useLegacyVersioning": {
-            "type": "boolean",
-            "description": "Whether to use the legacy versioning strategy. This value will be true in Nx v20 and false in Nx v21. The legacy versioning implementation will be removed in Nx v22, as will this flag.",
-            "default": false
-          },
-          "conventionalCommits": {
-            "type": "boolean",
-            "description": "Shorthand for enabling the current version of projects to be resolved from git tags, and the next version to be determined by analyzing commit messages according to the Conventional Commits specification.",
-            "default": false
-          },
-          "git": {
-            "$ref": "#/definitions/NxReleaseGitConfiguration"
-          },
-          "preVersionCommand": {
-            "type": "string",
-            "description": "A command to run after validation of nx release configuration, but before versioning begins. Useful for preparing build artifacts. If --dry-run is passed, the command is still executed, but with the NX_DRY_RUN environment variable set to 'true'."
-          },
-          "specifierSource": {
-            "type": "string",
-            "enum": ["prompt", "conventional-commits", "version-plans"],
-            "default": "prompt",
-            "description": "The source to use for determining the specifier to use when versioning. 'prompt' is the default and will interactively prompt the user for an explicit/imperative specifier. 'conventional-commits' will attempt determine a specifier from commit messages conforming to the Conventional Commits specification. 'version-plans' will determine the specifier from the version plan files available on disk."
-          },
-          "manifestRootsToUpdate": {
-            "type": "array",
-            "items": {
-              "oneOf": [
-                {
-                  "type": "string",
-                  "description": "Path to the directory containing a manifest file to update. Supports placeholders like {projectRoot} and {projectName}."
-                },
-                {
-                  "type": "object",
-                  "properties": {
-                    "path": {
-                      "type": "string",
-                      "description": "Path to the directory containing a manifest file to update. Supports placeholders like {projectRoot} and {projectName}."
-                    },
-                    "preserveLocalDependencyProtocols": {
-                      "type": "boolean",
-                      "description": "Whether to preserve local dependency references using protocols like 'workspace:' or 'file:'. Set this to false for dist files that need to be published if not using a package manager that swaps references at publish time like pnpm or bun.",
-                      "default": true
-                    }
+      "additionalProperties": false,
+      "properties": {
+        "conventionalCommits": {
+          "type": "boolean",
+          "description": "Shorthand for enabling the current version of projects to be resolved from git tags, and the next version to be determined by analyzing commit messages according to the Conventional Commits specification.",
+          "default": false
+        },
+        "git": {
+          "$ref": "#/definitions/NxReleaseGitConfiguration"
+        },
+        "preVersionCommand": {
+          "type": "string",
+          "description": "A command to run after validation of nx release configuration, but before versioning begins. Useful for preparing build artifacts. If --dry-run is passed, the command is still executed, but with the NX_DRY_RUN environment variable set to 'true'."
+        },
+        "specifierSource": {
+          "type": "string",
+          "enum": ["prompt", "conventional-commits", "version-plans"],
+          "default": "prompt",
+          "description": "The source to use for determining the specifier to use when versioning. 'prompt' is the default and will interactively prompt the user for an explicit/imperative specifier. 'conventional-commits' will attempt determine a specifier from commit messages conforming to the Conventional Commits specification. 'version-plans' will determine the specifier from the version plan files available on disk."
+        },
+        "manifestRootsToUpdate": {
+          "type": "array",
+          "items": {
+            "oneOf": [
+              {
+                "type": "string",
+                "description": "Path to the directory containing a manifest file to update. Supports placeholders like {projectRoot} and {projectName}."
+              },
+              {
+                "type": "object",
+                "properties": {
+                  "path": {
+                    "type": "string",
+                    "description": "Path to the directory containing a manifest file to update. Supports placeholders like {projectRoot} and {projectName}."
                   },
-                  "required": ["path"],
-                  "additionalProperties": false
-                }
-              ]
-            },
-            "description": "A list of directories containing manifest files (such as package.json) to apply updates to when versioning. By default, only the project root will be used, but you could customize this to only version a manifest in a dist directory, or even version multiple manifests in different directories, such as both source and dist."
-          },
-          "currentVersionResolver": {
-            "type": "string",
-            "enum": ["registry", "disk", "git-tag", "none"],
-            "description": "The resolver to use for determining the current version of a project during versioning. This is needed for versioning approaches which involve relatively modifying a current version to arrive at a new version, such as semver bumps like 'patch', 'minor' etc. Using 'none' explicitly declares that the current version is not needed to compute the new version, and should only be used with appropriate version actions implementations that support it."
-          },
-          "currentVersionResolverMetadata": {
-            "type": "object",
-            "additionalProperties": true,
-            "description": "Metadata to provide to the configured currentVersionResolver to help it in determining the current version. What to pass here is specific to each resolver."
-          },
-          "fallbackCurrentVersionResolver": {
-            "type": "string",
-            "enum": ["disk"],
-            "description": "The fallback version resolver to use when the configured currentVersionResolver fails to resolve the current version."
-          },
-          "versionPrefix": {
-            "type": "string",
-            "enum": ["auto", "", "~", "^", "="],
-            "default": "auto",
-            "description": "The prefix to use when versioning dependencies. This can be one of the following: auto, '', '~', '^', '=', where auto means the existing prefix will be preserved."
-          },
-          "deleteVersionPlans": {
-            "type": "boolean",
-            "description": "Whether to delete the processed version plans file after versioning is complete. This is false by default because the version plans are also needed for changelog generation.",
-            "default": false
-          },
-          "updateDependents": {
-            "type": "string",
-            "enum": ["never", "auto"],
-            "default": "auto",
-            "description": "When versioning independent projects, this controls whether to update their dependents (i.e. the things that depend on them). 'never' means no dependents will be updated (unless they happen to be versioned directly as well). 'auto' is the default and will cause dependents to be updated (a patch version bump) when a dependency is versioned."
-          },
-          "logUnchangedProjects": {
-            "type": "boolean",
-            "description": "Whether to log projects that have not changed during versioning.",
-            "default": true
-          },
-          "preserveLocalDependencyProtocols": {
-            "type": "boolean",
-            "description": "Whether to preserve local dependency protocols (e.g. file references, or the `workspace:` protocol in package.json files) of local dependencies when updating them during versioning. This was false by default in legacy versioning, but is true by default now.",
-            "default": true
-          },
-          "preserveMatchingDependencyRanges": {
-            "type": ["boolean", "array"],
-            "description": "Whether to preserve matching dependency ranges when updating them during versioning. This is false by default. (e.g. The new version will be '1.2.0' and the current version range in dependents is already '^1.0.0'. Therefore, the manifest file is not updated.)",
-            "default": false,
-            "items": {
-              "type": "string",
-              "enum": [
-                "dependencies",
-                "devDependencies",
-                "peerDependencies",
-                "optionalDependencies"
-              ]
-            }
-          },
-          "versionActions": {
-            "type": "string",
-            "description": "The path to the version actions implementation to use for releasing all projects by default. This can also be overridden on the release group and project levels.",
-            "default": "@nx/js/src/release"
-          },
-          "versionActionsOptions": {
-            "type": "object",
-            "description": "The specific options that are defined by each version actions implementation. They will be passed to the version actions implementation when running a release.",
-            "additionalProperties": true
-          }
-        }
-      },
-      "else": {
-        "properties": {
-          "useLegacyVersioning": {
-            "type": "boolean",
-            "description": "Whether to use the legacy versioning strategy. This value was true in Nx v20 and became false in Nx v21. The legacy versioning implementation will be removed in Nx v22, as will this flag.",
-            "default": false
-          },
-          "conventionalCommits": {
-            "type": "boolean",
-            "description": "Shorthand for enabling the current version of projects to be resolved from git tags, and the next version to be determined by analyzing commit messages according to the Conventional Commits specification.",
-            "default": false
-          },
-          "git": {
-            "$ref": "#/definitions/NxReleaseGitConfiguration"
-          },
-          "preVersionCommand": {
-            "type": "string",
-            "description": "A command to run after validation of nx release configuration, but before versioning begins. Useful for preparing build artifacts. If --dry-run is passed, the command is still executed, but with the NX_DRY_RUN environment variable set to 'true'."
+                  "preserveLocalDependencyProtocols": {
+                    "type": "boolean",
+                    "description": "Whether to preserve local dependency references using protocols like 'workspace:' or 'file:'. Set this to false for dist files that need to be published if not using a package manager that swaps references at publish time like pnpm or bun.",
+                    "default": true
+                  }
+                },
+                "required": ["path"],
+                "additionalProperties": false
+              }
+            ]
           },
-          "generator": {
+          "description": "A list of directories containing manifest files (such as package.json) to apply updates to when versioning. By default, only the project root will be used, but you could customize this to only version a manifest in a dist directory, or even version multiple manifests in different directories, such as both source and dist."
+        },
+        "currentVersionResolver": {
+          "type": "string",
+          "enum": ["registry", "disk", "git-tag", "none"],
+          "description": "The resolver to use for determining the current version of a project during versioning. This is needed for versioning approaches which involve relatively modifying a current version to arrive at a new version, such as semver bumps like 'patch', 'minor' etc. Using 'none' explicitly declares that the current version is not needed to compute the new version, and should only be used with appropriate version actions implementations that support it."
+        },
+        "currentVersionResolverMetadata": {
+          "type": "object",
+          "additionalProperties": true,
+          "description": "Metadata to provide to the configured currentVersionResolver to help it in determining the current version. What to pass here is specific to each resolver."
+        },
+        "fallbackCurrentVersionResolver": {
+          "type": "string",
+          "enum": ["disk"],
+          "description": "The fallback version resolver to use when the configured currentVersionResolver fails to resolve the current version."
+        },
+        "versionPrefix": {
+          "type": "string",
+          "enum": ["auto", "", "~", "^", "="],
+          "default": "auto",
+          "description": "The prefix to use when versioning dependencies. This can be one of the following: auto, '', '~', '^', '=', where auto means the existing prefix will be preserved."
+        },
+        "deleteVersionPlans": {
+          "type": "boolean",
+          "description": "Whether to delete the processed version plans file after versioning is complete. This is false by default because the version plans are also needed for changelog generation.",
+          "default": false
+        },
+        "updateDependents": {
+          "type": "string",
+          "enum": ["never", "auto", "always"],
+          "default": "auto",
+          "description": "When versioning independent projects, this controls whether to update their dependents (i.e. the things that depend on them). 'never' means no dependents will be updated (unless they happen to be versioned directly as well). 'auto' is the default and will cause dependents to be updated (a patch version bump) when a dependency is versioned, as long as a group or projects filter is not applied that does not include them. 'always' will cause dependents to be updated (a patch version bump) when a dependency is versioned, even if they are not included in the group or projects filter."
+        },
+        "logUnchangedProjects": {
+          "type": "boolean",
+          "description": "Whether to log projects that have not changed during versioning.",
+          "default": true
+        },
+        "preserveLocalDependencyProtocols": {
+          "type": "boolean",
+          "description": "Whether to preserve local dependency protocols (e.g. file references, or the `workspace:` protocol in package.json files) of local dependencies when updating them during versioning.",
+          "default": true
+        },
+        "preserveMatchingDependencyRanges": {
+          "type": ["boolean", "array"],
+          "description": "Whether to preserve matching dependency ranges when updating them during versioning. This is false by default. (e.g. The new version will be '1.2.0' and the current version range in dependents is already '^1.0.0'. Therefore, the manifest file is not updated.)",
+          "default": false,
+          "items": {
             "type": "string",
-            "description": "The generator implementation to use for versioning.",
-            "default": "@nx/js:release-version"
-          },
-          "generatorOptions": {
-            "type": "object",
-            "description": "These options will be passed to the configured \"release.version.generator\" (which will be \"@nx/js:release-version\" if not set explicitly).",
-            "additionalProperties": true
+            "enum": [
+              "dependencies",
+              "devDependencies",
+              "peerDependencies",
+              "optionalDependencies"
+            ]
           }
         },
-        "additionalProperties": false
+        "versionActions": {
+          "type": "string",
+          "description": "The path to the version actions implementation to use for releasing all projects by default. This can also be overridden on the release group and project levels.",
+          "default": "@nx/js/src/release"
+        },
+        "versionActionsOptions": {
+          "type": "object",
+          "description": "The specific options that are defined by each version actions implementation. They will be passed to the version actions implementation when running a release.",
+          "additionalProperties": true
+        }
       }
     },
     "NxReleaseGroupVersionConfiguration": {
       "type": "object",
-      "$comment": "We need to improve this configuration definition to be more precise once legacy versioning is removed. Right now it needs to be left open and runtime validation will ensure correct behavior.",
       "properties": {
         "groupPreVersionCommand": {
           "type": "string",
           "description": "A command to run after validation of nx release configuration AND after the release.version.preVersionCommand (if any), but before versioning begins for this specific group. Useful for preparing build artifacts for the group. If --dry-run is passed, the command is still executed, but with the NX_DRY_RUN environment variable set to 'true'."
+        },
+        "conventionalCommits": {
+          "type": "boolean",
+          "description": "Shorthand for enabling the current version of projects to be resolved from git tags, and the next version to be determined by analyzing commit messages according to the Conventional Commits specification.",
+          "default": false
+        },
+        "git": {
+          "$ref": "#/definitions/NxReleaseGitConfiguration"
+        },
+        "specifierSource": {
+          "type": "string",
+          "enum": ["prompt", "conventional-commits", "version-plans"],
+          "default": "prompt",
+          "description": "The source to use for determining the specifier to use when versioning. 'prompt' is the default and will interactively prompt the user for an explicit/imperative specifier. 'conventional-commits' will attempt determine a specifier from commit messages conforming to the Conventional Commits specification. 'version-plans' will determine the specifier from the version plan files available on disk."
+        },
+        "manifestRootsToUpdate": {
+          "type": "array",
+          "items": {
+            "oneOf": [
+              {
+                "type": "string",
+                "description": "Path to the directory containing a manifest file to update. Supports placeholders like {projectRoot} and {projectName}."
+              },
+              {
+                "type": "object",
+                "properties": {
+                  "path": {
+                    "type": "string",
+                    "description": "Path to the directory containing a manifest file to update. Supports placeholders like {projectRoot} and {projectName}."
+                  },
+                  "preserveLocalDependencyProtocols": {
+                    "type": "boolean",
+                    "description": "Whether to preserve local dependency references using protocols like 'workspace:' or 'file:'. Set this to false for dist files that need to be published if not using a package manager that swaps references at publish time like pnpm or bun.",
+                    "default": true
+                  }
+                },
+                "required": ["path"],
+                "additionalProperties": false
+              }
+            ]
+          },
+          "description": "A list of directories containing manifest files (such as package.json) to apply updates to when versioning. By default, only the project root will be used, but you could customize this to only version a manifest in a dist directory, or even version multiple manifests in different directories, such as both source and dist."
+        },
+        "currentVersionResolver": {
+          "type": "string",
+          "enum": ["registry", "disk", "git-tag", "none"],
+          "description": "The resolver to use for determining the current version of a project during versioning. This is needed for versioning approaches which involve relatively modifying a current version to arrive at a new version, such as semver bumps like 'patch', 'minor' etc. Using 'none' explicitly declares that the current version is not needed to compute the new version, and should only be used with appropriate version actions implementations that support it."
+        },
+        "currentVersionResolverMetadata": {
+          "type": "object",
+          "additionalProperties": true,
+          "description": "Metadata to provide to the configured currentVersionResolver to help it in determining the current version. What to pass here is specific to each resolver."
+        },
+        "fallbackCurrentVersionResolver": {
+          "type": "string",
+          "enum": ["disk"],
+          "description": "The fallback version resolver to use when the configured currentVersionResolver fails to resolve the current version."
+        },
+        "versionPrefix": {
+          "type": "string",
+          "enum": ["auto", "", "~", "^", "="],
+          "default": "auto",
+          "description": "The prefix to use when versioning dependencies. This can be one of the following: auto, '', '~', '^', '=', where auto means the existing prefix will be preserved."
+        },
+        "deleteVersionPlans": {
+          "type": "boolean",
+          "description": "Whether to delete the processed version plans file after versioning is complete. This is false by default because the version plans are also needed for changelog generation.",
+          "default": false
+        },
+        "updateDependents": {
+          "type": "string",
+          "enum": ["never", "auto"],
+          "default": "auto",
+          "description": "When versioning independent projects, this controls whether to update their dependents (i.e. the things that depend on them). 'never' means no dependents will be updated (unless they happen to be versioned directly as well). 'auto' is the default and will cause dependents to be updated (a patch version bump) when a dependency is versioned."
+        },
+        "logUnchangedProjects": {
+          "type": "boolean",
+          "description": "Whether to log projects that have not changed during versioning.",
+          "default": true
+        },
+        "preserveLocalDependencyProtocols": {
+          "type": "boolean",
+          "description": "Whether to preserve local dependency protocols (e.g. file references, or the `workspace:` protocol in package.json files) of local dependencies when updating them during versioning.",
+          "default": true
+        },
+        "preserveMatchingDependencyRanges": {
+          "type": ["boolean", "array"],
+          "description": "Whether to preserve matching dependency ranges when updating them during versioning. This is false by default. (e.g. The new version will be '1.2.0' and the current version range in dependents is already '^1.0.0'. Therefore, the manifest file is not updated.)",
+          "default": false,
+          "items": {
+            "type": "string",
+            "enum": [
+              "dependencies",
+              "devDependencies",
+              "peerDependencies",
+              "optionalDependencies"
+            ]
+          }
+        },
+        "versionActions": {
+          "type": "string",
+          "description": "The path to the version actions implementation to use for releasing all projects by default. This can also be overridden on the release group and project levels.",
+          "default": "@nx/js/src/release"
+        },
+        "versionActionsOptions": {
+          "type": "object",
+          "description": "The specific options that are defined by each version actions implementation. They will be passed to the version actions implementation when running a release.",
+          "additionalProperties": true
         }
       },
-      "additionalProperties": true
+      "additionalProperties": false
     },
     "NxReleaseChangelogConfiguration": {
       "type": "object",
@@ -1107,14 +1183,44 @@
     },
     "NxReleaseGroupDockerConfiguration": {
       "type": "object",
-      "$comment": "We need to improve this configuration definition to be more precise once legacy versioning is removed. Right now it needs to be left open and runtime validation will ensure correct behavior.",
       "properties": {
         "groupPreVersionCommand": {
           "type": "string",
           "description": "A command to run after validation of nx release configuration, but before docker versioning begins. Used for preparing docker build artifacts. If --dry-run is passed, the command is still executed, but with the NX_DRY_RUN environment variable set to 'true'. It will run in addition to the global `preVersionCommand`"
+        },
+        "skipVersionActions": {
+          "oneOf": [
+            {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "description": "Array of projects which should use a no-op VersionActions implementation rather than any potentially inferred by default or via Inference Plugins."
+            },
+            {
+              "type": "boolean",
+              "description": "When set to true, all projects in the release setup/release group will use a no-op VersionActions implementation."
+            }
+          ],
+          "description": "Projects which should use a no-op VersionActions implementation rather than any potentially inferred by default or via Inference Plugins. Can be an array of project names (subset of projects in the release setup/release group) or a boolean (true means all projects)."
+        },
+        "versionSchemes": {
+          "type": "object",
+          "additionalProperties": {
+            "type": "string"
+          },
+          "description": "Record of named version patterns to choose between when versioning docker projects. e.g. \"production\": \"{currentDate|YYMM.DD}.{shortCommitSha}\", \"hotfix\": \"{currentDate|YYMM.DD}-hotfix\""
+        },
+        "repositoryName": {
+          "type": "string",
+          "description": "Repository name for the image on the configured registry"
+        },
+        "registryUrl": {
+          "type": "string",
+          "description": "Url of the Docker Image/Container Registry to push images to. Defaults to Docker Hub."
         }
       },
-      "additionalProperties": true
+      "additionalProperties": false
     }
   }
 }