v0.25.2

Release notes

Fixed

• Wrong handling of command-line arguments in east util connect.
• Suppress integer to pointer cast pessimizes optimization opportunities, caused by LOG_* macros,
  when east codechecker check is run.

v0.25.1

Release notes

Fixed

• A bug where east install toolchain command wouldn't correctly detect supported versions
  from nrfutil-toolchain-manager.

v0.25.0

Release notes

Changed

• east util connect command now tries to determine the JLink's --speed option from the
  build directory's runners.yaml file. If that value is not present, it defaults to 4000.
  east util connect still accepts the --speed option, which will override the value from
  the build directory's runners.yaml file.

v0.24.1

Release notes

Fixed

• A bug where installed v2.8.0-rc1 toolchain would be confused for v2.8.0.

v0.24.0

Release notes

Added

• Support for installing non-release NCS versions of toolchain, such as v2.7.0-rc1. East will
  now correctly install such versions of the toolchain, if found in the west manifest file.

Fixed

• A bug in east build parsing introduced in v0.23.2.

v0.23.2

Release notes

Fixed

• east build is now a true pass-through command. Previously, the less used commands would
  silently get dropped. This now enables the use of the --snippet, --shield and other west build flags. Run east build --extra-help to see all the available options.

v0.23.1

Release notes

Fixed

• Parsing of west.yml when a project within the yaml does not contain the repo-path key.
• compile_commands.json file is now correctly copied from the build directory to the project
  directory and west top directory for Zephyr projects using sysbuild.
• Correctly propagate return code in case east codechecker servdiff fails.

v0.23.0

Release notes

Added

• east.yml now supports specifying samples in nested subdirectories. For example, if there is a
  sample located under samples/basic/blinky, it can be specified in east.yml simply as
  - name: basic/blinky. Samples build artefacts will be stored in the build directory under
  the same subdirectory structure. This feature allows users to organize their samples in a more
  structured way, instead of having all samples in the root samples directory.
  This feature is documented in the docs/configuration.md file under Samples section.
  Suggested by @Finwood in #111.

Fixed

• east release command, which failed to find project dir, when run with
  EAST_DONT_USE_TOOLCHAIN_MANAGER=1 option.
• east codechecker check, which previous failed to find compile_command.json file on
  builds that were using sysbuild.

v0.22.1

Release notes

Fixed

• The issue where build failure in east release command would just fail without warning.
  (#110).
• The issue where east release command wasn't creating artefacts for builds using sysbuild
  (#108).

v0.22.0

Release notes

Changed

• Remove self-detection of Docker environment (introduced in v0.21.0) and add support for
  EAST_DONT_USE_TOOLCHAIN_MANAGER environment variable. If this variable is set to 1,
  East will not try to use the toolchain manager, but will pass the commands directly to the
  system provided West.
  The rationale for this change is that some Docker environments don't provide all tools/commands
  and East should use toolchain-manager in that cases. That case is our current CI environment,
  where we just install East and want it to manage the tooling. But some Docker environments
  will provide all tools, including East, so East should just use them directly.
  But there is no way to detect this automatically, so we need to provide a way for the user to
  tell East what to do. This is done with the EAST_DONT_USE_TOOLCHAIN_MANAGER environment
  variable.