Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Failed to parse 0.1 into a Semantic Version (v 6.0.0-alpha.1) #3341

Closed
mtufe-delhaize opened this issue Jan 16, 2023 · 4 comments · Fixed by #3379
Closed

[Bug] Failed to parse 0.1 into a Semantic Version (v 6.0.0-alpha.1) #3341

mtufe-delhaize opened this issue Jan 16, 2023 · 4 comments · Fixed by #3379
Labels
Milestone

Comments

@mtufe-delhaize
Copy link

mtufe-delhaize commented Jan 16, 2023

Describe the bug
next-version is failed to parse 0.1 into a Semantic Version

Actual Behavior

Failed to parse 0.1 into a Semantic Version

Steps to Reproduce

Agent : ubuntu-latest or windows-latest
Azure Devops Pipeline GitVersion.Tools Preview
GitVersion.Tools v6.0.0-alpha.1

Context

GitVersion.yml

next-version: 0.1
assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: MajorMinorPatchTag
assembly-informational-format: '{InformationalVersion}'
mode: ContinuousDelivery
continuous-delivery-fallback-label : ci
increment: Inherit
label-prefix: '[vV]'
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)'
commit-message-incrementing: Enabled
commit-date-format: 'yyyy-MM-dd'
ignore:
  sha: []
merge-message-formats: {}
branches:
  master:
    regex: ^master$|^main$
    mode: ContinuousDelivery
    label: ''
    increment: Patch
    prevent-increment-of-merged-branch-version: true
    track-merge-target: false
    tracks-release-branches: false
    is-release-branch: false

Your Environment

Azure Devops Pipeline

  • Version Used: 6.0.0-alpha.1
  • Build Agent ubuntu-latest or windows-latest
@HHobeck
Copy link
Contributor

HHobeck commented Jan 17, 2023

I think it's broken because of a merge failure. We need to change this lines of code:

image

@HHobeck
Copy link
Contributor

HHobeck commented Jan 17, 2023

In advance you need to adapt the GitVersion.yml file and specify the label-prefix as optional: label-prefix: '[vV]?'

@arturcic
Copy link
Member

I think it's broken because of a merge failure. We need to change this lines of code:

image

@HHobeck I think beside this @mtufe-delhaize will need to add the
"semver-format": "Loose"

arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 17, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 17, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 17, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 17, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 17, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 18, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 18, 2023
arturcic added a commit to arturcic/GitVersion that referenced this issue Feb 18, 2023
arturcic added a commit that referenced this issue Feb 18, 2023
#3341 - fix parsing loose version format
@arturcic arturcic modified the milestones: 6.x, 6.0.0-beta.1 Mar 2, 2023
@arturcic
Copy link
Member

arturcic commented Mar 2, 2023

🎉 This issue has been resolved in version 6.0.0-beta.1 🎉
The release is available on:

Your GitReleaseManager bot 📦🚀

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 a pull request may close this issue.

3 participants