Configuration value for 'AssemblyVersioningScheme' has no value. (this should not happen, please report an issue)

[f-rich]

Prerequisites

• I have written a descriptive issue title
• I have searched issues to ensure it has not already been reported

GitVersion package

GitVersion.MsBuild

GitVersion version

6.5.1

Operating system

Windows

What are you seeing?

ERROR [25-12-11 12:25:29:94] An unexpected error occurred: 1> System.Exception: Configuration value for 'AssemblyVersioningScheme' has no value. (this should not happen, please report an issue) 1> at GitVersion.Configuration.EffectiveConfiguration..ctor(IGitVersionConfiguration configuration, IBranchConfiguration branchConfiguration, EffectiveConfiguration fallbackConfiguration) in /_/src/GitVersion.Core/Configuration/EffectiveConfiguration.cs:line 35 1> at GitVersion.VersionCalculation.NextVersionCalculator.FindVersion() in /_/src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 32 1> at GitVersion.GitVersionCalculateTool.CalculateVersionVariables() in /_/src/GitVersion.Core/Core/GitVersionCalculateTool.cs:line 45 1> at GitVersion.GitVersionExecutor.RunGitVersionTool(GitVersionOptions gitVersionOptions) in /_/src/GitVersion.App/GitVersionExecutor.cs:line 69

What is expected?

A successful build, I guess.

(message says to report the issue, so I am :-))

Steps to Reproduce

GitVersion.yml with:

mode: ManualDeployment
workflow: ""

RepositoryFixture Test

No response

Output log or link to your CI build (if appropriate).

[HHobeck]

Hi @f-rich,

If you specify a workflow with an empty string, it means you are not using any workflow template and are creating your own workflow from scratch. In that case, you need to provide all mandatory fields for it to work properly.

For backward-compatibility reasons, this property currently defaults to GitFlow/v1. In the next major release, the workflow property will become mandatory.

See the documentation for more details: https://gitversion.net/docs/reference/configuration

[f-rich]

Hi @HHobeck,

Thanks for the reply - I figured that was what was going on but the message said to report anyway, so I did :-)