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

Use GitVersion to determine package version to be produced #1061

Closed
Tracked by #1057
CharliePoole opened this issue Dec 29, 2021 · 1 comment · Fixed by #1063
Closed
Tracked by #1057

Use GitVersion to determine package version to be produced #1061

CharliePoole opened this issue Dec 29, 2021 · 1 comment · Fixed by #1063
Assignees
Milestone

Comments

@CharliePoole
Copy link
Collaborator

CharliePoole commented Dec 29, 2021

Currently, we always build the version coded in the build.cake file, like 3.13.0, except on AppVeyor where we generate a unique pre-release suffix. That means the versioning of a given build is different on the local machine and any other CI servers from what it is in appveyor. By using GitVersion to determine the next version to build, we will be building the same version for a given commit on all platforms.

@CharliePoole CharliePoole changed the title Use GitVersion to determine version rather than relying on AppVeyor features so that we create the same package versions on all platforms. Use GitVersion to determine package version to be produced Dec 29, 2021
@CharliePoole CharliePoole self-assigned this Dec 29, 2021
@mikkelbu mikkelbu added this to the 3.13.1 milestone Jan 1, 2022
@CharliePoole
Copy link
Collaborator Author

This issue has been resolved in version 3.13.1

The release is available on:
GitHub.
NuGet packages are also available NuGet.org and
Chocolatey Packages may be found at Chocolatey.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants