Skip to content

Releases: grisp/rebar3_grisp

2.8.0

12 Oct 12:43
2.8.0
bacb45e
Compare
Choose a tag to compare

Fixed

  • Fix the firmware and pack commands when a dependency is using semver.

Changed

  • Renamed the grisp firmware command argument --force-bundle/-F and the grisp
    pack command argument --force-bundle/-F to --refresh/-r. #91

Removed

  • The utility function rebar3_grisp_util:rebar_command/4 has been removed as it
    runs app_discovery provider again and that causes issues with dependencies
    using semver. Instead rebar3:run/1 is used. #91

Full Changelog: 2.7.0...2.8.0

2.7.0

06 Sep 18:41
2.7.0
7f0d445
Compare
Choose a tag to compare

What's Changed

Added

  • New -t/--tar option to the deploy command to save a grisp release tarball in
    the _grisp/deploy directory.
  • New firmware command to generate GRiSP 2 binary firmwares: #83
  • New pack command to generate GRiSP 2 software update package: #85

Changed

  • The deploy destination in rebar.config is now optional if the -t/--tar option
    is specified to the deploy command. To disable a copy deployment when
    configured in rebar.config, an empty destination can be specified on the
    command line: --destination="".

Full Changelog: 2.6.1...2.7.0

2.6.1

21 Jun 09:51
2.6.1
9ef7b6d
Compare
Choose a tag to compare

Changed

  • Adapation to the new format of the prompt provided by grisp_tools_configure:settings/0: #81
  • User input are now asked using events for configure task: #81

Full Changelog: 2.6.0...2.6.1

2.6.0

07 May 15:35
2.6.0
b93ba20
Compare
Choose a tag to compare

Added

  • New rebar3 grisp configure command to create a custom GRiSP application. It replaces the command rebar3 new grispapp as a new way to create a custom GRiSP application: #78

Removed

  • Removed the grispapp template: #78

Fixed

  • CI update to only test OTP 24 and 25: #79

New Contributors

Full Changelog: 2.5.0...2.6.0

2.5.0

21 Apr 09:55
2.5.0
35c9c4f
Compare
Choose a tag to compare

Added

  • New rebar3 grisp report command: groups and packs usefull debug information
    about the current grisp project
  • New rebar.config option {docker, "grisp/grisp2-rtems-toolchain"} is available for the grisp toolchain. Allows to use a docker image instead of a local installation.

Changed

  • Set default Erlang version to "25.2.3" in grispapp template

Full Changelog: 2.4.0...2.5.0

2.4.0

18 Jul 13:51
2.4.0
Compare
Choose a tag to compare

Added

  • A --cached flag to rebar3 grisp package list to list only cached
    packages
  • Support for OTP 24

Fixed

  • Crash when listing packages
  • Download skipped if using OTP package cache

Full Changelog: 2.3.0...2.4.0

2.3.0

07 Jun 13:59
2.3.0
Compare
Choose a tag to compare

Added

  • Exact OTP version selection, e.g. '=23.3'
  • Toolchain validation before building

Changed

  • The OTP Git repository is more thoroughly checked for consistency

Fixed

  • Deploy and build tasks now works offline
  • Extracted packages are cached globally instead of per project
  • Custom builds now correctly uses OTP versions from Git
  • rebar3 package list now sorts versions correctly

New Contributors

Full Changelog: 2.2.2...2.3.0

2.2.2

01 Mar 17:30
Compare
Choose a tag to compare

Fixed

  • Fix processing of already downloaded OTP packages (through grisp_tools)

Full Changelog: 2.2.1...2.2.2

2.2.1

01 Mar 09:12
2.2.1
b5ec11a
Compare
Choose a tag to compare

Added

  • Automatically pick the highest version when only the release name is
    specified during deployment (#64)
  • rebar3 grisp package list can now list both OTP and toolchain packages. In
    addition, it can display only certain columns.
  • OTP Git cloning is now shallow (using --dethp 1) which more than halves the
    download time of OTP sources.

Fixed

  • Deploys no longer crash on invalid release names or versions (#68)

Full Changelog: 2.2.0...2.2.1

2.2.0

16 Feb 10:02
2.2.0
d8629ae
Compare
Choose a tag to compare

Added

  • rebar3 grisp package list can now take a --hash flag that prints all hash versions of a package

Changed

  • Deploying without a custom OTP build will correctly pick a version from
    existing pre-built packages or show a proper error