Skip to content

Conversation

@pocketninja25
Copy link
Contributor

@pocketninja25 pocketninja25 commented Apr 11, 2025

Attempt to fix issue where some nuget packages would forcibly update themselves to a higher version when performing a restore on the command line. #709

Reynolds, Daniel added 2 commits April 11, 2025 13:28
…zo#709)

Attempt to fix issue where some nuget packages would forcibly update themselves to a higher version when performing a restore on the command line.
@bigswede74
Copy link

@JoC0de @GlitchEnzo , Small PR here, shouldn’t take more than a few minutes to review.

@JoC0de
Copy link
Collaborator

JoC0de commented May 4, 2025

@pocketninja25 sorry for the delay, and thanks for providing the fix. I merged it. Would be nice if you test if it fixes the issue. The GitHub action outputs the newest release as a .unitypackage or you can install it using the "Git" install method. Would be nice if I know if the fix works before releasing a new version.

@JoC0de JoC0de merged commit db9853e into GlitchEnzo:master May 4, 2025
8 checks passed
@pocketninja25
Copy link
Contributor Author

This version does appear to fix the issue we were having. Succesfully tried it on a couple of projects

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When using GitHub Nuget feed, "restore" and "install" updates to latest version rather than the (older) version in packages.config

3 participants