Problem

When using {versionActionsVersion} to manage Docker image versioning, we typically only need a single version scheme:

"docker": {
  "versionSchemes": {
    "default": "{versionActionsVersion}"
  }
}

Any version modifications (pre-id, etc.) are handled upstream before the release.

Currently, even with a single scheme defined, the system prompts the user to select it — unless --dockerVersionScheme or --dockerVersion is explicitly passed. This adds unnecessary friction to the release process.

Solution

Auto-select the version scheme when only one is available, skipping the prompt entirely.

Before

nx release --projects=my-app
> ? What type of docker release would you like to make for project "my-app"? (Use arrow keys)
> ❯ default

After

nx release --projects=my-app
> Using version scheme "default" for project "my-app"

No prompt. No extra CLI arguments needed.

Changes

• Skip version scheme prompt when only one scheme is configured
• Moved single-scheme detection into promptForNewVersion for cleaner separation
• Added tests for both single and multiple scheme scenarios