-
Notifications
You must be signed in to change notification settings - Fork 652
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
[Improvement] Remove legacy version variables and related configuration options in v6 #2325
Labels
Milestone
Comments
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions. |
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 26, 2022
arturcic
added a commit
that referenced
this issue
May 26, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 27, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 27, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 27, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 27, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 27, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 27, 2022
arturcic
added a commit
to arturcic/GitVersion
that referenced
this issue
May 28, 2022
arturcic
added a commit
that referenced
this issue
May 31, 2022
🎉 This issue has been resolved in version 6.0.0 🎉 Your GitReleaseManager bot 📦🚀 |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently have quite a few version variables and related configuration options that are tailored towards sytems that don't support SemVer 2.0, such as
LegacySemVerPadding
,BuildMetaDataPadding
,CommitsSinceVersionSourcePadding
, etc.We should remove these in v6, at least from Core. If pepole still need these, we should look into adding them through an extension to the Core somehow.
The text was updated successfully, but these errors were encountered: