Installing updated packages using buffrs install
fails when a package is already locked to a prior version
#187
Labels
bug
Reports or fixes associated with bugs in this project
complexity::medium
Issues or ideas which require some discussion, research and more implementation work
component::cli
Everything related to the buffrs cli
docs::project
Documenting the project vision, design decisions etc
priority::high
Urgent change or idea, please review quickly
Milestone
Reproduce:
Given a project
foo
that depends onbar@=0.1.0
:buffrs install
which install[email protected]
and creates aProto.lock
bar@=0.2.0
buffrs install
againBuffrs now complains about being unable to install
bar@=0.2.0
asbar@=0.1.0
is locked. This is not the intended behavior as the manifest, and edits to the manifest are always the source of truth and the lockfile is a) intended to enable reproducibility and b) behave frictionless.The current fix is to
rm Proto.lock && buffrs install
which is neither user friendly nor the point of having the lockfile.The text was updated successfully, but these errors were encountered: