6.8.1

[arturcic]

---

This discussion was created from the release 6.8.1.

[neslekkim]

Using this version in Bitbucket Pipelines crashed, pipeline build stopped, no information in the log, nothing at all, but last that came in the log was information about gitversion installed.
So I ran GitVersion locally, and 6.6 works fine, 6.7 works fine, but 6.81. does not

This is the error I'm getting:

ERROR [26-07-03 17:15:55:96] An unexpected error occurred: System.ArgumentException: 'BranchName' is not a valid placeholder at GitVersion.Formatting.StringFormatWithExtension.EvaluateMatch(String input, Func2 memberEvaluator, IEnvironment environment) in //src/GitVersion.Core/Formatting/StringFormatWithExtension.cs:line 122
at GitVersion.Formatting.StringFormatWithExtension.<>c__DisplayClass6_0.b__0(Match match) in //src/GitVersion.Core/Formatting/StringFormatWithExtension.cs:line 76
at System.Text.RegularExpressions.Regex.<>c.b__99_0(ValueTuple5& state, Match match) at System.Text.RegularExpressions.Regex.RunAllMatchesWithCallback[TState](String inputString, ReadOnlySpan1 inputSpan, Int32 startat, TState& state, MatchCallback1 callback, RegexRunnerMode mode, Boolean reuseMatchObject) at System.Text.RegularExpressions.Regex.RunAllMatchesWithCallback[TState](String input, Int32 startat, TState& state, MatchCallback1 callback, RegexRunnerMode mode, Boolean reuseMatchObject)
at System.Text.RegularExpressions.Regex.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat)
at System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator)
at GitVersion.Formatting.StringFormatWithExtension.FormatWith(String template, Func2 memberEvaluator, IEnvironment environment) in /_/src/GitVersion.Core/Formatting/StringFormatWithExtension.cs:line 76 at GitVersion.Formatting.StringFormatWithExtension.FormatWith(String template, IDictionary2 source, IEnvironment environment) in //src/GitVersion.Core/Formatting/StringFormatWithExtension.cs:line 69
at GitVersion.Configuration.ConfigurationExtensions.GetBranchSpecificLabel(EffectiveConfiguration configuration, String branchName, String branchNameOverride, IEnvironment environment) in //src/GitVersion.Core/Extensions/ConfigurationExtensions.cs:line 136
at GitVersion.Configuration.ConfigurationExtensions.GetBranchSpecificLabel(EffectiveConfiguration configuration, ReferenceName branchName, String branchNameOverride, IEnvironment environment) in //src/GitVersion.Core/Extensions/ConfigurationExtensions.cs:line 119
at GitVersion.VersionCalculation.TaggedCommitVersionStrategy.GetBaseVersionsInternal(EffectiveBranchConfiguration configuration)+MoveNext() in //src/GitVersion.Core/VersionCalculation/VersionSearchStrategies/TaggedCommitVersionStrategy.cs:line 48
at GitVersion.VersionCalculation.NextVersionCalculator.GetNextVersions(IVersionStrategy versionStrategy, EffectiveBranchConfiguration effectiveBranchConfiguration, IGitVersionConfiguration configuration)+MoveNext() in //src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 290
at GitVersion.VersionCalculation.NextVersionCalculator.GetNextVersions(EffectiveBranchConfiguration effectiveBranchConfiguration, IGitVersionConfiguration configuration)+MoveNext() in //src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 277
at GitVersion.VersionCalculation.NextVersionCalculator.<>c__DisplayClass15_0.<g__GetNextVersionsInternal|0>d.MoveNext() in /_/src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 257
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source) at GitVersion.VersionCalculation.NextVersionCalculator.GetNextVersions(IBranch branch, IGitVersionConfiguration configuration) in /_/src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 249 at GitVersion.VersionCalculation.NextVersionCalculator.CalculateNextVersion(IBranch branch, IGitVersionConfiguration configuration) in /_/src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 162 at GitVersion.VersionCalculation.NextVersionCalculator.FindVersion() in /_/src/GitVersion.Core/VersionCalculation/VersionCalculators/NextVersionCalculator.cs:line 54 at GitVersion.GitVersionCalculateTool.CalculateVersionVariables() in /_/src/GitVersion.Core/Core/GitVersionCalculateTool.cs:line 47 at GitVersion.GitVersionExecutor.RunGitVersionTool(GitVersionOptions gitVersionOptions) in /_/src/GitVersion.App/GitVersionExecutor.cs:line 66 INFO [26-07-03 17:15:55:96] Please run git log --graph --format="%h %cr %d" --decorate --date=relative --all --remotes=*to see the git graph. This can help you troubleshoot any issues.

and this is my GitVersion.yml, i could not find that BranchName was deprecated in the docs?

assembly-versioning-scheme: MajorMinorPatchTag mode: ContinuousDelivery commit-message-incrementing: Disabled branches: main: mode: ContinuousDelivery prevent-increment: of-merged-branch: true track-merge-target: false release: regex: release(es)?[/-] mode: ContinuousDeployment label: '{BranchName}' increment: Patch prevent-increment: of-merged-branch: false track-merge-target: true tracks-release-branches: true is-release-branch: true source-branches: ['main', 'release'] development: regex: dev(elop)?(ment)?$ mode: ContinuousDelivery label: '{BranchName}' increment: Minor prevent-increment: of-merged-branch: false track-merge-target: true tracks-release-branches: true is-release-branch: false source-branches: ['main']
And yes, maybe this config is not good, i don't understand everything in it, but it gives me the versioninfo i need so far :)

[arturcic]

hey @robertcoltheart will you have time for this PR? so that we can close this feature and release?

[HHobeck]

Agree, I think that we could keep the non throwing behavior in 6.8.2, and throw in 7.x. btw 6.8.x I think will be the latest version in 6.x

For version 7.x, I would recommend setting the workflow property to mandatory. Or changing the behavior that the template GitHubFlow/v1 will be not used as a fallback.

[asbjornu]

I'm actually not sure about this one. If correcting a mistake breaks old usage, and the breakage isn't massive (i.e. several issues being submitted daily), I think it's fine to keep the breaking behavior.

[neslekkim]

Works for me, I'm changing my config, trying to explore the config options a bit to see how they work, and what they do for the output.
It was just unexpected since I didn't know my config was flawed since it worked until that update, so I guess break on bad config should be ok?

[robertcoltheart]

hey @robertcoltheart will you have time for this PR? so that we can close this feature and release?

Will submit a PR tonight

[arturcic]

@robertcoltheart do you mind checking this one?