Skip to content

Conversation

@rmvangun
Copy link
Contributor

It is now possible to specify a semver cliVersion range in contexts/_template/metadata.yaml. This will cause an error to throw if the CLI version and blueprint requirement are not a match.

Signed-off-by: Ryan VanGundy 85766511+rmvangun@users.noreply.github.com

Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
…e metadata

It is now possible to specify a semver range in `contexts/_template/metadata.yaml` as `cliVersion`. This will prevent launching blueprints with incompatible CLI versions if set.

Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
@rmvangun rmvangun merged commit 27aaaac into main Nov 15, 2025
11 checks passed
@rmvangun rmvangun deleted the feature/blueprint-version-checks branch November 15, 2025 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants