Hello.
I noticed if shard.yml has
dependencies:
kemal:
github: sdogruyol/kemal
branch: master
and shard.lock says
kemal:
github: sdogruyol/kemal
commit: f916bad09568582a74730a38b40bdeceaab46a10
if I do a
$ shards install
it adds a new dependency into shard.lock that is in kemal/master, but isn't in the commit I am currently using....
In this case it added
+ exception_page:
+ github: crystal-loot/exception_page
Shards is confused between branch: master and the locked commit. It probably resolves dependencies using the shard.yml from the master branch, when it should really use the locked commit...
The install command should inject the locked constraints sooner, in order to force a locked commit.
Perfect, works great now, thank you!
Most helpful comment
Shards is confused between
branch: masterand the locked commit. It probably resolves dependencies using the shard.yml from the master branch, when it should really use the locked commit...The install command should inject the locked constraints sooner, in order to force a locked commit.