Johannes Müller

Ah, right. I believe that should be in `.gitignore` then. And `doc` should not be.

I don't like this because I don't want `shards` to become more of a build tool. It should focus on managing dependencies, and IMO does not need advanced build features....

I can't reproduce this with a fresh `shard.yml` + `shards install`. Can you provide the full `shard.lock` please? And try if it reproduces for you when you remove `shard.lock` and...

Oh wait, I had the wrong crystal version in path. It really depends on resolving against Crystal version 1.0.0. With 0.36.1 it works.

Yes, it reproduces with 1.0.0. It's really confusing that `neo4j` installs with `crystal: 0.34.0`.

Since the release of `[email protected]` the original configuration doesn't reproduce any more. Adding `version: "

I missed yesterday that `CRYSTAL_VERSION=1.0.0 shards install` already fails, not just `shards outdated`. So this is not specific to the outdated command. The core of the issue is that shards...

@daliborfilus I have no explanation why this is happening to you. It doesn't reproduce with my setup, as it did not on your second computer. So my guess would be...

> `>= 0.35.0` does not satisfy 1.0.0 No, it does. `1.0.0 >= 0.35.0` is totally correct. So if shards with `CRYSTAL_VERSION=1.0.0` reports unsatisfied requirement `crystal (>= 0.35.0)`, that's an error....

Indeed, you're right.