doc: west v0.14 release notes

Document this bug fix release.

Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
This commit is contained in:
Martí Bolívar 2022-08-29 06:48:26 -07:00 committed by Carles Cufí
parent f3de8c2c3b
commit f3fdfa3ff5
2 changed files with 30 additions and 1 deletions

View file

@ -26,7 +26,7 @@ You can run ``west --help`` (or ``west -h`` for short) to get top-level help
for available west commands, and ``west <command> -h`` for detailed help on
each command.
The following pages document west's ``v0.13.x`` releases, and provide additional
The following pages document west's ``v0.14.x`` releases, and provide additional
context about the tool.
.. toctree::

View file

@ -3,6 +3,35 @@
West Release Notes
##################
v0.14.0
*******
Bug fixes:
- West commands that were run with a bad local configuration file dumped stack
in a confusing way. This has been fixed and west now prints a sensible error
message in this case.
- A bug in the way west looks for the zephyr repository was fixed. The bug
itself usually appeared when running an extension command like ``west build``
in a new workspace for the first time; this used to fail (just for the first
time, not on subsequent command invocations) unless you ran the command in
the workspace's top level directory.
- West now prints sensible error messages when the user lacks permission to
open the manifest file instead of dumping stack traces.
API changes:
- The ``west.manifest.MalformedConfig`` exception type has been moved to the
``west.configuration`` module
- The ``west.manifest.MalformedConfig`` exception type has been moved to the
:ref:`west.configuration <west-apis-configuration>` module
- The ``west.configuration.Configuration`` class now raises ``MalformedConfig``
instead of ``RuntimeError`` in some cases
v0.13.1
*******