-
Notifications
You must be signed in to change notification settings - Fork 53
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
For release branches there's a conflict while publishing NuGet package #616
Comments
@pascalberger just seeing this one now. This really comes down to the configuration of GitVersion I think. How would you see this being resolved? |
Having the first build with a version number published and subsequent ones skipped doesn't seem like a good option to me. If we're going to publish CI package for every version, version numbers should be unique for every build IMHO. |
I would suggest making use of the |
But is it really helpful if you have a CI package available for the first build with a specific version, but not from any subsequent builds? IMHO this is just confusing |
When running multiple commits on a release/hotfix branch, GitVersion doesn't assert a unique version number unless a tag is applied. To counteract this, concatenate to asserted version number, to make a new unique one, when running on a release/hotfix branch.
@pascalberger I believe this has been addressed, and we also discussed the other issue we spoke about on tonights stream, but I think that will need additional testing. |
* release/2.0.0: (340 commits) (GH-697) Update JetBrains.ReSharper.CommandLineTools reference from 2020.2.3 to 2020.2.4 Add rule URL resolver for CakeContrib-Guidelines Update Cake.Issues.Recipe to 0.4.3 (GH-691) Update JetBrains.ReSharper.CommandLineTools reference from 2020.2.2 to 2020.2.3 Revert "(GH-673) Use .Net Global Tool for ReSharper Tools" (GH-616) Create unique version number Update Cake.Issues.Recipe to 0.4.2 (GH-687) using RepositoryName insteadof repositoryName to make use of the default-value for RepositoryName. (GH-612) Add docs for upgrading to 2.0.0 (GH-673) Use .Net Global Tool for ReSharper Tools Update Cake.Issues.Recipe to 0.4.1 (GH-684) parameter ShouldDocumentSourceFiles is no longer dependent on ShouldGenerateDocumentation. (GH-677) Updated documentation to reflect the changes of the default of webLinkRoot (GH-680) Documentation of GH-680 as a known-issue. (GH-677) set default for WebLinkRoot as RepositoryName instead of title. (GH-675) Update Cake.Transifex reference from 0.9.0 to 0.9.1 (maint) Switch to latest version of Kudu (GH-674) Update github action workflow with cake-action (GH-674) update bootstrappers to run use .NET Core global tool (maint) Correct line endings for shell scripts ...
Merge branch 'release/2.0.0' into master * release/2.0.0: (340 commits) (GH-697) Update JetBrains.ReSharper.CommandLineTools reference from 2020.2.3 to 2020.2.4 Add rule URL resolver for CakeContrib-Guidelines Update Cake.Issues.Recipe to 0.4.3 (GH-691) Update JetBrains.ReSharper.CommandLineTools reference from 2020.2.2 to 2020.2.3 Revert "(GH-673) Use .Net Global Tool for ReSharper Tools" (GH-616) Create unique version number Update Cake.Issues.Recipe to 0.4.2 (GH-687) using RepositoryName insteadof repositoryName to make use of the default-value for RepositoryName. (GH-612) Add docs for upgrading to 2.0.0 (GH-673) Use .Net Global Tool for ReSharper Tools Update Cake.Issues.Recipe to 0.4.1 (GH-684) parameter ShouldDocumentSourceFiles is no longer dependent on ShouldGenerateDocumentation. (GH-677) Updated documentation to reflect the changes of the default of webLinkRoot (GH-680) Documentation of GH-680 as a known-issue. (GH-677) set default for WebLinkRoot as RepositoryName instead of title. (GH-675) Update Cake.Transifex reference from 0.9.0 to 0.9.1 (maint) Switch to latest version of Kudu (GH-674) Update github action workflow with cake-action (GH-674) update bootstrappers to run use .NET Core global tool (maint) Correct line endings for shell scripts ...
…orrect semantic version number Hotfix and Release branches should use the unique semantic version number - implemented in (cake-contribGH-616). To fully implement as intended, the logic for applying the correct semantic version format needs to ensure that the 'is tagged' check is applied to each of the branch types.
Using Cake.Recipe 2.0.0-alpha0319 I get the following error after running builds for subsequent commits on a release branch:
See Log
The text was updated successfully, but these errors were encountered: