-
Notifications
You must be signed in to change notification settings - Fork 25
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
increase major version (2.0.0) and update packages #425
increase major version (2.0.0) and update packages #425
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only 1 concern
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="8.0.0" PrivateAssets="All" /> | ||
<PackageReference Include="System.Threading.Channels" Version="6.0.0" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to upgrade these 2? For maximum bundles compatibility (we'll be releasing this in an existing bundles feed) I'd rather not majorly increase dependencies that we don't strictly need. We'll get another chance, with more time, to see if it's safe to increase this once we consume DF WebJobs V3, so I'd prefer to delay these major version increases until then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am getting downgrade warnings if I don't include "System.Threading.Channels" Version="6.0.0" , must be being picked up somewhere. Build fails.
I don't like those warnings, I would rather go to 6.0.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that:
- I can entirely remove reference to System.Threading.Channels because it is implicitly imported now by EH
- Sourcelink is a build-time only dependency so I don't think there is an issue with keeping it there.
In preparation of the 2.0.0 release: