Version requirement breaking Amber

[dburnsii]

The release of version v0.3.5 includes a requirement for a recent release of crystal-lang/crystal-db ~> v0.7.0. The dependencies for the currently released version of Amber (v0.30.1) and previous releases point to ~> v0.6.0. This is causing shards install to fail, and any project without a shard.lock file pointing to the correct versions fails to build.

A fix for this is to re-release this shard as version v0.3.x, with the version selection of crystal-db removed. Including the version is a good idea though, and it should be released with version v0.4.x to include the change without breaking existing projects.

Discussed with @elorest and he confirmed this as a solution.

[elorest]

Previous to 0.3.5 micrate pointed to crystal-db without a version. When crystal-db was just updated micrate automatically points to the newest version, while all other shards which depended on crystal-db correctly pointed to 0.6.0. This broke all past and present versions of amber. I'm going to fix this now by:

1. Releasing 0.3.5 to point to 0.6.0 of crystal-db.
2. Releasing 0.4.0 to point to 0.7.0 of crystal-db.

[drujensen]

Sorry. Should have bumped minor for this. - dru

…

Sent from my iPhone

On Sep 27, 2019, at 2:26 PM, Isaac Sloan ***@***.***> wrote:  Previous to 0.3.5 micrate pointed to crystal-db without a version. When crystal-db was just updated micrate automatically points to the newest version, while all other shards which depended on crystal-db correctly pointed to 0.6.0. This broke all past and present versions of amber. I'm going to fix this now by: Releasing 0.3.5 to point to 0.6.0 of crystal-db. Releasing 0.4.0 to point to 0.7.0 of crystal-db. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[elorest]

That's fine. Thanks for working on it.