Closed veelenga closed 3 years ago
Is the new way of specifying the Crystal version (crystal: ">= ..."
) backwards compat with older crystal/shards version? Not sure how I should bump the version here
Actually (I didn't test it) but I doubt this shard even works with 0.31.0
. Maybe I will just bump to 1.0.0 and make min crystal 1.0.0 too
The version is already bumped in master (but not released):
I pointed awscr-s3 to awscr-singer@master and it started to work. So I assume no changes needed in this repo, just a new release.
Oh right, thanks!
awscr-s3 points to awscr-signer@v0.8.1, which does not satisfy the crystal 1.0.0 compatibility. See for details:
https://github.com/crystal-community/timecop.cr/pull/7#issuecomment-815505128
Actions to be taken: