You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A couple of times i have used a NuGet package that i do not want to upgrade, because of a breaking change in the update, leading me to leave a note somewhere about not upgrading that package. The problem is, when updating NuGet packages, people might not see those notes, and end up upgrading anyway, leading to a break in the program.
It might be nice to have a feature within the UI to lock/freeze a package to a specific version with an optional note where an explanation as to why this is the case and conditions to be met before it would be wise to upgrade it. The freeze would mean the package would not be updated unless unfrozen first.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A couple of times i have used a NuGet package that i do not want to upgrade, because of a breaking change in the update, leading me to leave a note somewhere about not upgrading that package. The problem is, when updating NuGet packages, people might not see those notes, and end up upgrading anyway, leading to a break in the program.
It might be nice to have a feature within the UI to lock/freeze a package to a specific version with an optional note where an explanation as to why this is the case and conditions to be met before it would be wise to upgrade it. The freeze would mean the package would not be updated unless unfrozen first.
Beta Was this translation helpful? Give feedback.
All reactions