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.

v0.19.1

Release notes

Fixed

• Fix a case where user would install toolchain with east and
  then get a message that toolchain is not installed, when trying to
  build.

v0.19.0

Release notes

Changed

• Bump PyYAML to support Python3.12 and up (#106).
• Make tox to support Python3.12 and up.

Fixed

• Resolve invalid escape sequence '.' warnings (#106).

v0.18.3

Release notes

Fixed

• Perform check for nrfutil-toolchain-manager after determining that the east
  was run inside the NCS project.

v0.18.2

Release notes

Fixed

• Add a --no-py flag to the east util cortex-debug. It fixes possible
  issues with RTT in VSCode.