-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shards build repeatedly fetches already satisfied dependencies #353
Comments
What version of shards are you using? |
0.10.0 locally and 0.8.1 in production and in local development docker instances |
@damianham can you share your 0.10 wasn't properly checking installed versions when locking without a release tag. This is hopefully fixed already for the next version. |
shard.yml
shard.lock
|
Thanks @damianham! In this case So, this is already fixed! |
Actually, I'll reopen this and add a specific integration test to the suite to avoid regressions in the future. |
@waj many thanks for your efforts, very much appreciated. |
When issuing a shards build target_name command the dependencies are fetched EVERY time even though
-- the dependencies are already installed in the lib folder and all dependencies are satisfied
-- the dependencies were satisfied only moments ago in the previous build command in the develop - build - debug cycle
Not a problem for people on super fast network in London/San Francisco but for digital nomads in far flung places it is a pain in the neck.
The text was updated successfully, but these errors were encountered: