Update the lock file when necessary #110
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR is created as a draft, as it includes changes from #109.
Closes #83.
CLI changes
protofetch fetch
: updatesprotofetch.lock
ifprotofetch.toml
has changed. Previous behavior: ignoreprotofetch.toml
even if changed, fetch whateverprotofetch.lock
says.protofetch fetch --locked
: verifies that the lock file is up-to-date and fails otherwiseprotofetch fetch --force-lock
: deprecated, but still works for backwards compatibility.protofetch update
: recreates the lock file, likefetch --force-lock
used to, but does not actually fetch the protosIt is possible to keep
--force-lock
, but I think it'd better to deprecate this flag:API changes
fetch
andlock
now accept aLockMode
enum.Compatibility
fetch --locked
will not succeed unless the updated lock file is available.