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

Compatibility warning when running against Cake v1.0.0 #49

Closed
wazzamatazz opened this issue Feb 24, 2021 · 3 comments · Fixed by #50
Closed

Compatibility warning when running against Cake v1.0.0 #49

wazzamatazz opened this issue Feb 24, 2021 · 3 comments · Fixed by #50
Milestone

Comments

@wazzamatazz
Copy link

Expected Behavior

When using Cake.Json in a build script that uses Cake 1.0.0, there should not be any compatibility warnings displayed.

Current Behavior

Using the latest version (5.2.0) of Cake.Json with Cake 1.0.0 causes a warning message during build:

The assembly 'Cake.Json, Version=5.2.0.0, Culture=neutral, PublicKeyToken=null' is referencing an older version of Cake.Core (0.35.0). 
For best compatibility it should target Cake.Core version 1.0.0.

Possible Solution

Update Cake.Json to target Cake 1.0.0.

Context

This issue has no real impact beyond a mildly annoying warning message, as there do not seem to be any actual compatibility issues.

@gep13
Copy link
Member

gep13 commented Feb 24, 2021

@wazzamatazz 👋

This is on my list of addins to get updated to use Cake 1.0.0. Should hopefully get to this later this week.

@wazzamatazz
Copy link
Author

Great, thanks!

nils-a added a commit to nils-a/Cake.Json that referenced this issue Feb 26, 2021
@gep13 gep13 added this to the 6.0.0 milestone Feb 26, 2021
@gep13 gep13 closed this as completed in #50 Feb 26, 2021
@cake-contrib-bot
Copy link

🎉 This issue has been resolved in version 6.0.0 🎉

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants