v0.16.3

Release notes

Fixed

• Error build message in east release command. It was also prettified.
• Build type issue when building app not listed in the east.yaml, again.
  See (#85) for the start of the issue and 7243ee4 for solution and rationale.

v0.16.1

Release notes

Changed

• Transition to the trunk-based development model.

Fixed

• Incorrect conversion of output of a git command into endpoint in
  east store command.

v0.16.0

Release notes

Added

• Version check. East will now occasionally check for the latest version and notify
  the user when it is available.
• Add EAST_CODECHECKER_CI_MODE environment variable. If running CodeChecker inside
  continuous integration environment, run export EAST_CODECHECKER_CI_MODE=1 before
  running any east codechecker commands. This will make east use the CodeChecker
  executable that is on the system path instead of the one in the tooling directory.
  System provided CodeChecker will normally also want to use the system provided
  clang, clang-tidy and cppcheck programs. way users can leverage the programs
  provided by continuous integration environment and not by east, which is usually
  faster due to caching.
• Add --build-dir option to the east codechecker commands. From now on, you do not
  need to run east codechecker command from the same directory where build folder
  is located. The default is still build, however you can specify a different one
  with --build-dir option.
• east codechecker commands now also take build directory location into account when
  generating a skip file.

Changed

• How previous build type of previously run build is detected. Previously east
  looked into the image_preload.cmake file and parsed its content to figure out the
  used build type. This approach worked well until someone wanted to append extra
  .conf files to the CONFIG_OVERLAY. To support this use case east now just
  creates a single file in the build dir and writes build type to it.

v0.15.2

Release notes

Fixed

• Incorrect message that was shown when toolchain was not installed.
• Fix east release for driver projects, which do not have app folder.

v0.15.1

Release notes

Removed

• Python version check. This was mostly needed due to Conda binary, which is
  not used any more.

Fixed

• Platform detection for clang tooling.

v0.15.0

Release notes

Breaking interface changes

• This version of East created breaking changes in the interface. This was
  done due to the consistency with existing west interface.
  Changes:
  • east sys-setup was removed and replaced with east install.
  • east install now contains several subcommands, which can be used to
    install codechecker, toolchain, nrfutil-toolchain-manager, etc.
  • east update is now just a wrapper around west update command.
  • Newly added east init is now just a wrapper around west init command.

Added

• Support for Codechecker, a static analysis infrastructure. Newly added
  command east codechecker contains several subcommands:
  • Users can now check their Zephyr projects with clang-tidy and
    clangsa,
  • apply suggested fixes with fixit,
  • store the results of the Codechecker analysis to a server,
  • servdiff - compare the local analysis against the last server analysis,
  • See example codechecker_config.yaml file with example-config,
  • or directly run any Codechecker command with bypass.
    An effort was made to make the east codechecker check command most useful:
  • Most of the warnings that are reported because of the Zephyr's macros are
    filtered out.
  • Installation of Codechecker and all its dependencies is seamless, you only
    need to run east install codechecker.
• Support for generating the Software Bill of Materials (SBOM) in SPDX format.
  To generate SPDX files add --spdx or --spdx-app-only flags to
  east build or east release respectively. east build command will place
  SPDX files in the build folder, while east release will generate them for
  each combination of parameters and place them next to the respective
  artefacts.
• Add EAST_BUILD_TYPE CMake define to the build and release commands.
  This define is emitted only if we are building an app with build type
  functionality (so, it is not emitted for samples). It contains a string,
  identical to the given --build-type flag.

Fixed

• Build type issue when building app not listed in the east.yaml (#85)
• pykwalify error caused by an empty east.yml (#85)
• Always delete build folder when build settings do not match. (#85)
• Incorrect removal of toolchain when using --force flag. (#85)
• Improve error message when running bypass in non NCS repo. (#85)
• Correctly handle ctrl+c when running east debug. Previously everything
  broke (yes, everything), when user wanted to stop a running program inside
  gdb. Essentially the ctrl+c combination was passed twice to gdb, which
  caused all sort of problems.

Removed

• Conda from list of installed tools. Conda was originally intended to be used
  as bootstrapping environment, however there was never need for it.

v0.14.0

Release notes

Added

• Add --shell flag to the east bypass command. It launches a sub-shell within the
  current terminal inside the isolated environment provided by the Nordic's nRF
  Toolchain Manager.
• east twister command. This command is just a wrapper for the west twister
  command which runs Twister, a test runner tool.
• east attach command. This command is just a wrapper for the west attach
  command, which is similiar to the west debug.

Changed

• east bypass now passes arbitrary commands into directly into the Nordic's nRF
  Toolchain Manager instead into just West that is in the Manager. That way user can
  user use other executables and python programs provided by the toolchains in the
  Manager.
• east build, east flash and east debug are now just wrappers for their
  west counterparts. Due to this the internals and externals of the East could
  be simplified. User experience did not change, the commands behave just like
  they did before, they just do not directly provide help for possible
  options and arguments, but instead instruct users to use --extra-help
  option to learn more about west command counterparts. Due to this change the
  attach command was moved from debug command to its own place.

v0.13.0

Release notes

Removed

• Conda install from east sys-setup command as it is not needed by East.

v0.12.3

Release notes

Fixed

• Use HOME environmental variable instead of USER to determine home
  directory.

v0.12.2

Release notes

Fixed

• USER environmental variable is not present on GitHub Action Runners, so
  East should not assume that is present.