How do I update a *single* package dependency when I am using lock files? #12802
Unanswered
tbutler-qontigo
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is my scenario:
1.*
Foo
v1.2.3
andBar
v4.5.6
-ForceEvaluate
to ensure the build uses the latest, and I will check in any changes to thepackages.lock.json
file-LockedMode
to ensure that the versions never change in my release from what existing at the time the rc was taken.Foo
andBar
continue to be worked on and have been updated in our nuget repo tov1.2.4
andv4.5.7
respectively => develop branch builds will get these, which is fine.What happens now if I need to patch the release (or production!) and only update component
Bar
so I getv4.5.7
? I am using-LockedMode
so I will always getv1.2.3
andv4.5.6
respectively for the components at the moment.If I
-ForceEvaluate
in my release build then both components will be updated rather than just the one that is required for this release fix, which is not what I want.So how do I only update one package (and I guess potentially it's dependencies if something has had to change there)?
I don't really want to have to mess about with manually editing the lock file(s) and ideally I wouldn't have to for example change the version in the
.csproj
file to be an explicit one (Which, alone, does not seem to be enough anyway) because then when merging back down to the develop branch I would have to remember to ignore/undo that specific change.thanks
Beta Was this translation helpful? Give feedback.
All reactions