-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Cake.GitVersioning v3.6+ doesn't support Cake v2.x anymore #934
Comments
Similar issue here:
Seems to work when SDK in globals.json is .NET 6 or above but e.g. not with .NET Core 3.1 |
The .NET Core 3.1 target framework was removed from Nerdbank.GitVersioning.Tasks in 49ff64c. According to .NET and .NET Core Support Policy, Microsoft stopped supporting .NET Core 3.1 on December 13, 2022. I don't know how the Cake dependency change was decided. According to Security Policy, Cake 2.x.x is still supported. |
To clarify, for me it's more of a documentation issue rather than an issue of the addin itself. If such changes are reflected in the release notes or with a major version upgrade, this should be ok I think. |
Thank you for the feedback. I've updated the release notes. I'm not a Cake user myself, so my acceptance of the Dependabot PR to upgrade the reference assembly was made somewhat ignorantly of how it would likely impact users. Would Cake v3 users be able to use NB.GV if it were compiled against Cake v2? |
Maybe I find some time tonight to check this... |
I'm about to release a servicing fix for 3.6 and would like to close this issue as part of that. @kapsiR how is that testing coming? Should I downgrade to referencing Cake v2 again? |
Sorry for the delay, my time in the evening is very limited at the moment... As of my tests, it seems to work with a warning (Cake v3.0.0 and Cake.GitVersioning built with Cake.Core v2.3.0):
|
This fixes a regression of 3.6.99-alpha+56b1dacf89, Cake v2.x wasn't supported anymore Fixes dotnet#934
This fixes a regression of 3.6.99-alpha+56b1dacf89, Cake v2.x wasn't supported anymore Fixes dotnet#934
Is this an intended change in
v3.6
(3.6.99-alpha+56b1dacf89)? I couldn't find anything regarding it in the release notes...The text was updated successfully, but these errors were encountered: