Skip to content

Unable to create a Release with non-semver versioning #9919

@calverp

Description

@calverp

Severity

Blocking any customers using non-semver versioning, 1 known instance impacted

Version

2026.2.1361

Latest Version

I could reproduce the problem in the latest build

What happened?

When trying to create a new release with non-semver versioning ("prod-271c680") it is blocked due to the auto-increment not being able to run.

The auto-increment shouldn't need to run as a version is being manually supplied

Reproduction

  • Create a new release
  • Input a non-semver version e.g. "prod-271c680"
  • Hit Save

Error and Stacktrace

The version template for project 'Misc' generated 'prod-271c6803'. Versions that do not start with a numeric component cannot be auto-incremented on future releases. Check the template does not include variables that resolve to non-numeric text.

More Information

Looks to be related to this PR: https://github.com/OctopusDeploy/OctopusDeploy/pull/41199

Workaround

If you create a the release with a semver compliant version, you can then edit the release afterwards to have your desired non-semver version number.

Metadata

Metadata

Assignees

Labels

kind/bugThis issue represents a verified problem we are committed to solving

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions