Skip to content

Releases: crenv/crystal-build-cr

v0.1.6 - 2022-10-10

10 Oct 17:56
6dd3430
Compare
Choose a tag to compare

Fixed

  • Explicitly set the Shards installation versions for Crystal versions from 1.1.0 through the latest 1.6.0.

Added

  • Ability to manually specify a shards version to be installed alongside Crystal with the --shards-version flag. This will only apply to installations that would otherwise fetch and build Shards from source as a result of Shards not being bundled with Crystal.

Changed

  • Release builds are now done with Ubuntu 20.04 instead of 16.04.
  • Release builds are now done with Crystal 1.6.0 instead of 0.35.1.

v0.1.5 - 2021-03-22

22 Mar 22:45
b1a7c16
Compare
Choose a tag to compare

Fixed

  • Explicitly set the Shards installation versions for Crystal 0.36.0, 0.36.1, and 1.0.0.

Congratulations to the Crystal team and all contributors on the launch of Crystal 1.0.0!

v0.1.4 - 2021-01-11

12 Jan 02:53
ca6aee5
Compare
Choose a tag to compare

Added

  • A success message will be printed at the end of a successful installation.
  • A verbose flag (-v, --verbose) has been added which will make the installation process quite noisy. The default, non-verbose output should now be nearly silent.

Changed

  • The -v flag will now correspond to enabling verbose mode (as mentioned above) instead of being a shorthand version of the --version flag.
  • The Shards builder/installer process should now be a little smarter. For now, there is an exhaustive list of Crystal versions and a designated Shards version that each one maps to, that should be built to accompany it. I think I got everything working, but it's possible that for some older versions of Crystal, there are version mismatches that are incompatible. If you find any, please open an issue.
  • Shards build/install will be skipped for versions of Crystal earlier than 0.9.0, as the Shards GitHub releases page does not have releases earlier than that.

Fixed

  • The Shards builder/installer process should now select the correct make command/flag syntax based on the version of Shards selected to be installed. Previously this would have caused Shards to be built without a release flag for Shards versions >= 0.11.0.

v0.1.3 - 2020-06-23

24 Jun 04:26
1341888
Compare
Choose a tag to compare

Changed

  • The Crystal version is now 0.35.1.

Fixed

  • The version number wasn't updated in the previous release in all places, so it might say it's 0.1.1 instead of 0.1.2. This release should properly display 0.1.3.

v0.1.2 - 2020-01-27

28 Jan 06:41
40369b3
Compare
Choose a tag to compare

Added

  • Shards will now be built and installed automatically if not included in the Crystal tarball.

Changed

  • Parsing the downloaded tarball structure is no longer done at runtime - the download source now stores information on how the tarball is structured. This may be an issue in the future if the tarball structure is changed, but not retroactively.

Added

  • MIT license
  • A test for the install process

0.1.1

21 Jan 07:39
0f76777
Compare
Choose a tag to compare

Fixed

  • The runtime operating system should now be determined on-the-fly, and is no longer hard-coded to macOS. If we're unable to determine the OS, it will default to the latest Linux. If unable to determine bitness/bit-depth of the current OS, it will default to 64-bit.
  • Fail gracefully when no version number is provided as an argument.
  • Fixed -h, --help option not being present in help text

0.1.0

20 Jan 17:24
75f2469
Compare
Choose a tag to compare

Initial release. Largely untested.

Always downloads macos-x64 binaries until I can figure out an easy way to determine the runtime architecture and platform. Theoretically it would work on Linux if it was recompiled with this line changed from darwin to linux.