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.

v0.21.4

Release notes

Fixed

• east install nrfutil-toolchain-manager until now only checked if the nrfutil
  binary is present, but not also if the toolchain-manager package is installed
  inside it. That resulted in situations where the install command would report
  success, however any other east command after it would fail. Now the install
  command checks if the nrfutil binary is present and if the toolchain-manager
  package is installed inside it.

v0.21.3

Release notes

Fixed

• Relax the PyYAML requirement from exact version (PyYAML==6.0.2) to a range
  (PyYAML>=6.0.0). This prevents pip conflicts with the CodeChecker package
  (which wants ==6.0.0) in the CI.

v0.21.2

Release notes

Fixed

• east build command silently dropped the board-related .conf files when build types
  were used. This bug was introduced in the v0.20.0. with the adoption of the new hardware
  model naming.

v0.21.1

Release notes

Fixed

• east release command wrongly aborted, if a board from east.yml wasn't found
  in project's board directory. That was wrong, since the board might be located
  either in Zephyr, NCS or some other Zephyr module.

v0.21.0

Release notes

Added

• Make east compatible with Docker. When inside the docker environment East will
  not try to pass any commands to the nRFUtil's toolchain-manager,
  but it will pass them directly to the west.
  The rationale for that is that the docker environment should provide
  all commands that are needed for working on a Zephyr/NCS project and
  east should just use them directly.

v0.20.0

Release notes

Added

• Make build-types key in east.yml optional for applications. Until now it was
  mandatory, which forced users to define build types for applications, even if
  they didn't need them.
• East now supports hardware model v2 naming.

Changed

• Migrate to using toolchain-manager with nrfutil instead of a standalone
  nrfutil-toolchain-manager.exe executable. Instead of downloading the
  nrfutil-toolchain-manager.exe executable from a Nordic's project on the
  GitHub, use Nordic's nRF Util. Due to this change the East is now also
  supports MacOS. Additionally, toolchains from v2.7.0 and up can now be
  installed.
• Update project requirements to the latest versions.

Fixed

• Due to the adoption of the Sysbuild, the location of runners.yaml file could
  be different. Commands such as east util connect and
  east util cortex-debug use this file to determine the --device flag that
  is then passed to the JLink. East will now use domains.yaml file (if present
  )to determine the location of the runners.yaml file, otherwise it will use
  the default location.