6.0.0-rc.1

[arturcic]

---

This discussion was created from the release 6.0.0-rc.1.

[DSpirit]

Thanks for the update, glad to see it progressing :)

Unfortunately our current pipelines broke due to following issue:

Could not build the configuration instance because following exception occurred: 'Property 'tracks-merge-target' not found on type 'GitVersion.Configuration.BranchConfiguration'.' Please ensure that the /overrideconfig parameters are correct and the configuration file is in the correct format.

I've already tried adding these properties

tracks-merge-target: false
tracks-merge-message: true

in my GitVersion.yml:

workflow: GitHubFlow/v1
tag-prefix: '[vV]?'
update-build-number: true
strategies:
- MergeMessage
- TaggedCommit
- TrackReleaseBranches
- VersionInBranchName
- TrunkBased
merge-message-formats:
  AzureDevOps: 'Merged PR (?<PullRequestNumber>\d+) from (?<SourceBranch>[^\s]*) into (?<TargetBranch>[^\s]*)'
branches:
  main:
    regex: ^master$|^main$
    mode: ContinuousDeployment
    label: 'ci'
    is-source-branch-for:
    - feature
    - hotfix
    - release
    tracks-merge-target: false
    tracks-merge-message: true
  feature:
    regex: ^feature(s)?[/-](?<StoryNo>[A-Za-z0-9]+)?
    mode: ContinuousDelivery
    label: 'beta.{StoryNo}'
    increment: Minor
    tracks-merge-target: false
    tracks-merge-message: true
  hotfix:
    regex: ^(hot|bug)fix(es)?[/-](?<StoryNo>[#A-Za-z0-9]+)?
    mode: ContinuousDelivery
    label: 'beta.{StoryNo}'
    increment: Patch
  pull-request:
    regex: ^(pull|pull\-requests|pr)[/-]
    label: 'alpha'
    label-number-pattern: '[/-](?<number>\d+)'
    source-branches: [ 'main' ]
  release:
    regex: ^release(s)?[/-](?<BranchName>.+)
    label: 'rc'
    is-release-branch: true
  unknown:
    increment: Inherit
    regex: (?<BranchName>.+)
ignore:
  sha: []

but it's still failing. Is there anything I'm missing?

[HHobeck]

I think there is a typo in the GitHubFlow/v1 template:

• tracks-merge-target needs to be track-merge-target
• tracks-merge-message needs to be track-merge-message

[DSpirit]

Does the default template affect the run? Assuming the template is getting read as-is, the error message throws on every run as it wouldn't be able to parse the configuration.
I've created a PR to fix the typos here: #4041

[HHobeck]

As a workaround for now: If you specify the workflow with an empty string value means you are not using a base template and you are configuring from scratch. Of course you need to provide the whole configuration in your file (without typo) to have the GitHubFlow up and running:

workflow: ''
assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: MajorMinorPatch
tag-prefix: '[vV]?'
version-in-branch-pattern: (?<version>[vV]?\d+(\.\d+)?(\.\d+)?).*
major-version-bump-message: '\+semver:\s?(breaking|major)'
minor-version-bump-message: '\+semver:\s?(feature|minor)'
patch-version-bump-message: '\+semver:\s?(fix|patch)'
no-bump-message: '\+semver:\s?(none|skip)'
tag-pre-release-weight: 60000
commit-date-format: yyyy-MM-dd
merge-message-formats: {}
update-build-number: true
semantic-version-format: Strict
strategies:
- Mainline
- ConfiguredNextVersion
...

[DSpirit]

Thank you! For now, I've just set the last beta version manually, waiting for the fix to be released.
However, I will keep track of the changes and adjust our configuration accordingly asap.

Thanks again for the quick support! I really appreciate the collaboration.

[HHobeck]

Sorry I was mistaken you need to specify the workflow to empty string.

[sergio-barja-uve]

Hi! I'm very interested in this new version and the feature 1839 Configurable next-version strategies and mode.
Do you have some estimation about when will 6.0.0 be available? Thanks!

[arturcic]

We hopefully will have a new RC released soon, and after that if everything goes well we release the 6.0.0 version. We are now focusing on improving the documentation and the release process

[HHobeck]

@arturcic Could you please give us an update what the next steps are? Thanks in advance.

[arturcic]

I would need to get this fixed and then we can release rc2. Give it a bit of time for the feedback from the community, and then release 6.0.0

[shoden]

Hi, first of all kudos for this project! I am starting to use it at work and I think it is an awesome tool.
I am wondering about the current version of GitVersion itself, as there is already a 6.0.0 version at hub.docker.com while this project is still in 5.12.0. I understand there is a 6.0.0-rc.1 docker image, how come there is already a 6.0.0? Thanks!

[HHobeck]

Hi, first of all kudos for this project! I am starting to use it at work and I think it is an awesome tool. I am wondering about the current version of GitVersion itself, as there is already a 6.0.0 version at hub.docker.com while this project is still in 5.12.0. I understand there is a 6.0.0-rc.1 docker image, how come there is already a 6.0.0? Thanks!

I don't see any version with a tag 6.0.0. Do you have a link? https://hub.docker.com/r/gittools/gitversion/tags?page=&page_size=&ordering=&name=6.0.0

[shoden]

The first tag in this search: https://hub.docker.com/r/gittools/gitversion/tags?page=&page_size=&name=6.0.0&ordering=-name
The tag page: https://hub.docker.com/layers/gittools/gitversion/6.0.0/images/sha256-ed617e6ba79bda7bbf29d1a31ee48b4708855547c6c6061464e64e259c620640?context=explore

[HHobeck]

The first tag in this search: https://hub.docker.com/r/gittools/gitversion/tags?page=&page_size=&name=6.0.0&ordering=-name The tag page: https://hub.docker.com/layers/gittools/gitversion/6.0.0/images/sha256-ed617e6ba79bda7bbf29d1a31ee48b4708855547c6c6061464e64e259c620640?context=explore

@arturcic Can you please take a look? Thank you in advance.

[arturcic]

@shoden , @HHobeck this will be fixed in rc2