-
Notifications
You must be signed in to change notification settings - Fork 451
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
Update dependencies #1815
Update dependencies #1815
Conversation
81976f4
to
ec06e96
Compare
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.
Thanks for the clear commit messages about each type of dependency update.
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.
This PR on its own does not actually address all outstanding Component Detection issues: clearlydefined/curated-data#28383 needs to be accepted first, maybe with modifications once/if spdx/license-list-XML#2550 gets addressed. After that, I'll have to re-run the Azure Pipeline that performs the Component Detection.
<PackageReference Include="GitForWindows.GVFS.Installer" Version="$(GitPackageVersion)" /> | ||
<PackageReference Include="GitForWindows.GVFS.Portable" Version="$(GitPackageVersion)" /> | ||
<PackageReference Include="GitForWindows.GVFS.Installer" Version="2.20220414.4" /> | ||
<PackageReference Include="GitForWindows.GVFS.Portable" Version="2.20220414.4" /> |
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.
Oops. I guess that this should be adjusted elsewhere...
The primary reason is that Component Detection (https://github.com/microsoft/component-detection) pointed out that the version we used is missing legal information. As of clearlydefined/curated-data#23677, version 6.2.1 of this package has a documented license. Therefore, this issue should be hereby resolved. Besides, it's always good to stay up to date with dependencies. Signed-off-by: Johannes Schindelin <[email protected]>
The primary reason is that Component Detection (https://github.com/microsoft/component-detection) pointed out that the version we used is missing legal information. Noticing that https://www.nuget.org/packages/LibGit2Sharp.NativeBinaries/2.0.278/License shows only a link into the repository, but the full license is shown at https://www.nuget.org/packages/LibGit2Sharp.NativeBinaries/2.0.322/License this issue should be hereby resolved. Besides, it's always good to stay up to date with dependencies. Since libgit2 is very careful about backwards-compatibility (and therefore LibGit2Sharp, too), this update should not result in any change of behavior. Signed-off-by: Johannes Schindelin <[email protected]>
Now that we addressed the Component Detection issues, let's just go ahead and proactively update the remaining dependencies, too. Signed-off-by: Johannes Schindelin <[email protected]>
ec06e96
to
56f001a
Compare
@derrickstolee would you mind having another look, just for completeness' sake? |
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.
Took another look for the latest iteration.
In reaction to Component Detection pointing out two more issues where dependencies are missing legal information, this PR updates the dependencies (all of them, including the two pointed out by Component Detection) to their latest stable versions.
This includes updating the InnoSetup dependency to a newer version, the LibGit2Sharp dependency to a newer version, and all remaining dependencies to their latest stable versions.