# Handling the new dependency resolver **URL:** \ **Category:** Help & Support\ **Created:** [June 30, 2020, 4:54pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294 "2020-06-30T16:54:12Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![jwoertink](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jwoertink/32/50_2.png) [@jwoertink](https://forum.crystal-lang.org/u/jwoertink)\ **Post date:** [June 30, 2020, 4:54pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/1 "2020-06-30T16:54:12Z")
I was trying to update the Lucky website, and when running `shards install`, I get this error. I’m wonder how others are handling this? ```auto Unable to satisfy the following requirements: - `crystal (~> 0.35, >= 0.35.0)` required by `lucky 0.23.0` - `crystal (~> 0.35, >= 0.35.0)` required by `authentic 0.6.1` - `crystal (~> 0.35, >= 0.35.0)` required by `carbon 0.1.2` - `crystal (~> 0.35, >= 0.35.0)` required by `habitat 0.4.4` - `crystal (~> 0.35, >= 0.35.0)` required by `dexter 0.3.1` - `crystal (~> 0.33, >= 0.33.0)` required by `exception_page 0.1.4` - `crystal (~> 0.33, >= 0.33.0)` required by `cry 0.4.2` - `crystal (~> 0.22, >= 0.22.0)` required by `shell-table 0.9.2+git.commit.078a04ea58ead5203bb435a3b5fff448ddabaeea` - `crystal (~> 0.35, >= 0.35.0)` required by `lucky_router 0.3.0` - `crystal (~> 0.35, >= 0.35.0)` required by `avram 0.16.0` - `crystal (~> 0.26, >= 0.26.1)` required by `wordsmith 0.2.0` - `crystal (~> 0.35, >= 0.35.0)` required by `lucky_cli 0.23.0` - `crystal (~> 0.35, >= 0.35.0)` required by `lucky_flow 0.7.0` - `crystal (~> 0.34, >= 0.34.0)` required by `cadmium_transliterator 0.1.0+git.commit.6ee68d64869ade8f39d2ec16cae3c7b80d5a4805` - `crystal (~> 0.35, >= 0.35.0)` required by `markd 0.2.1+git.commit.620845abb6776d1765d20d86cc0220aa40f89a91` - `crystal (< 1.0.0)` required by `dotenv 0.7.0` - `crystal (< 1.0.0)` required by `blank 0.1.0` - `crystal (< 1.0.0)` required by `pg 0.21.1` - `crystal (~> 0.35, >= 0.35.0)` required by `teeplate 0.8.2` - `crystal (~> 0.35, >= 0.35.0)` required by `selenium 0.6.0` - `crystal (~> 0.35, >= 0.35.0)` required by `webdrivers 0.3.0` - `crystal (~> 0.25, >= 0.25.0)` required by `db 0.9.0` - `crystal (~> 0.34, >= 0.34.0)` required by `future 0.1.0` - `crystal (~> 0.35, >= 0.35.1)` required by `crystar 0.1.7` Failed to resolve dependencies ``` ---
**Author:** ![jhass](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jhass/32/1779_2.png) [@jhass](https://forum.crystal-lang.org/u/jhass)\ **Post date:** [June 30, 2020, 7:58pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/2 "2020-06-30T19:58:02Z")
> > > In the wild: > https://github.com/oprypin/crystal-chipmunk/runs/796810944?check\_suite\_focus=true#step:16:12 > My shard became not installable as a dependency ever since crystal-1.0.0-dev. > I think that (despite @jhass hinting that this might... ---
**Author:** ![jwoertink](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jwoertink/32/50_2.png) [@jwoertink](https://forum.crystal-lang.org/u/jwoertink)\ **Post date:** [June 30, 2020, 8:08pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/3 "2020-06-30T20:08:29Z")
ah, thanks! ---
**Author:** ![asterite](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/asterite/32/60_2.png) [@asterite](https://forum.crystal-lang.org/u/asterite)\ **Post date:** [June 30, 2020, 8:22pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/4 "2020-06-30T20:22:50Z")
Is this running against crystal nightly? Otherwise I can’t see why this error would trigger. ---
**Author:** ![jwoertink](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jwoertink/32/50_2.png) [@jwoertink](https://forum.crystal-lang.org/u/jwoertink)\ **Post date:** [June 30, 2020, 8:24pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/5 "2020-06-30T20:24:20Z")
Nope, crystal 0.35 on Github Actions: `image: crystallang/crystal:0.35.0` ---
**Author:** ![jwoertink](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jwoertink/32/50_2.png) [@jwoertink](https://forum.crystal-lang.org/u/jwoertink)\ **Post date:** [June 30, 2020, 8:32pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/6 "2020-06-30T20:32:28Z")
OMG… there’s 2 containers… 1 specified the version, and the other didn’t … Ok, I see what you meant by nightly. 😅 ---
**Author:** ![Blacksmoke16](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/blacksmoke16/32/1241_2.png) [@Blacksmoke16](https://forum.crystal-lang.org/u/Blacksmoke16)\ **Post date:** [June 30, 2020, 8:34pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/7 "2020-06-30T20:34:09Z")
To be clear, `crystallang/crystal:0.35.0` would be `0.35.0`, and `crystallang/crystal` would be the latest release, i.e. `0.35.1`. Nightlies are in their own dedicated image. ---
**Author:** ![jwoertink](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jwoertink/32/50_2.png) [@jwoertink](https://forum.crystal-lang.org/u/jwoertink)\ **Post date:** [June 30, 2020, 8:35pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/8 "2020-06-30T20:35:55Z")
Ah, ok. That’s good to know. ---
**Author:** ![asterite](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/asterite/32/60_2.png) [@asterite](https://forum.crystal-lang.org/u/asterite)\ **Post date:** [June 30, 2020, 8:46pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/9 "2020-06-30T20:46:58Z")
So why did it fail? Did it run against nightly? ---
**Author:** ![jwoertink](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/jwoertink/32/50_2.png) [@jwoertink](https://forum.crystal-lang.org/u/jwoertink)\ **Post date:** [July 1, 2020, 2:51pm UTC](https://forum.crystal-lang.org/t/handling-the-new-dependency-resolver/2294/10 "2020-07-01T14:51:22Z")
I’m not sure the version it ran against, but it was a combination of the 2 containers being different versions and then caching them. As well as cashing shards. I removed cache, and updated the versions and it all worked. Oh, and I also used the `--ignore-crystal-version` on my `shards install`.