Lines Matching full:manifest
48 - The manifest file format now supports a ``description`` field in each
55 :ref:`west-manifest-rev`.
75 - ``west.manifest.Project`` now has a ``description`` attribute,
77 in the manifest data.
87 workspace against the manifest.
89 - Support for a new ``manifest.project-filter`` configuration option.
90 See :ref:`west-config-index` for details. The ``west manifest --freeze``
91 and ``west manifest --resolve`` commands currently cannot be used when
95 warnings. These warnings are errors if the new ``manifest.project-filter``
116 - ``west.manifest.Manifest.is_active()`` now respects the
117 ``manifest.project-filter`` configuration option's value.
124 - Manifest schema version "1.0" is now available for use in this release. This
126 used by applications that do not wish to use a "0.x" manifest "version:"
127 field. See :ref:`west-manifest-schema-version` for details on this feature.
220 open the manifest file instead of dumping stack traces.
224 - The ``west.manifest.MalformedConfig`` exception type has been moved to the
227 - The ``west.manifest.MalformedConfig`` exception type has been moved to the
238 - When calling west.manifest.Manifest.from_file() when outside of a
247 - You can now associate arbitrary user data with the manifest repository
248 itself in the ``manifest: self: userdata:`` value, like so:
252 manifest:
258 - The path to the manifest repository reported by west could be incorrect in
262 ``west.manifest`` API module.
264 - The ``west.Manifest.ManifestProject.__repr__`` return value was fixed
281 - The path handling in the ``west.manifest`` package has been overhauled in a
285 - ``west.manifest.Manifest.validate()``: this now returns the validated data as
289 - ``west.manifest.Manifest``: new:
294 from ``manifest: self: userdata:``, or is None
297 - ``west.manifest.ManifestProject``: new ``userdata`` attribute, which also
298 contains the parsed value from ``manifest: self: userdata:``, or is None
300 - ``west.manifest.ManifestImportFailed``: the constructor can now take any
302 <west-manifest-import-map>` or other compound value.
323 - West manifest files can now contain arbitrary user data associated with each
329 the manifest repository; it now prints ``N/A`` ("not applicable")
334 - The ``west.manifest.Project.userdata`` attribute was added to support
347 - The manifest file parser was incorrectly allowing project names which contain
356 - The changes made in west v0.10.1 to the ``west init --manifest-rev`` option
357 which selected the default branch name were leaving the manifest repository
372 ``west init --manifest-rev`` option value, if given, must now be either a
375 request can no longer be passed to ``--manifest-rev``. Users must now fetch
380 - ``west.manifest.Manifest.get_projects()`` avoids incorrect results in
383 - ``west.manifest.Project.sha()`` now works correctly for tag revisions.
406 avoids issues if the URL changes in the manifest file from when the submodule
412 - the :ref:`west-apis-manifest` module has fixed docstrings for the Project
420 - The :ref:`west-init` command's ``--manifest-rev`` (``--mr``) option no longer
434 <west-manifest-submodules>` is now optional.
438 - West now checks that the manifest schema version is one of the explicitly
439 allowed values documented in :ref:`west-manifest-schema-version`. The old
441 version where the ``manifest: version:`` key was introduced. This incorrectly
446 - A manifest file's ``group-filter`` is now propagated through an ``import``.
448 top level manifest file's ``group-filter`` had any effect; the group filter
454 The new behavior will take effect if ``manifest: version:`` is not given or
456 manifest file only with an explicit ``manifest: version: 0.9``. See
457 :ref:`west-manifest-schema-version` for more information on schema versions.
468 - Commands like ``west manifest --resolve`` now correctly include group and
491 manifest imports is discouraged. The resulting behavior has changed in west
496 - West manifests now support :ref:`west-manifest-submodules`. This allows you
501 - West manifests now support :ref:`west-manifest-groups`. Project groups can be
529 - A manifest file with an empty ``manifest: self: path:`` value is invalid, but
537 - added ``west.manifest.Manifest.is_active()``
538 - added ``west.manifest.Manifest.group_filter``
539 - added ``submodules`` attribute to ``west.manifest.Project``, which has
540 newly added type ``west.manifest.Submodule``
544 - The :ref:`west-manifest-import` feature now supports the terms ``allowlist``
553 This is a feature release which changes the manifest schema by adding support
557 - Manifest import mappings now support a ``path-prefix:`` key, which places
559 See :ref:`west-manifest-ex3.4` for an example.
563 - :ref:`west manifest --path <west-manifest-path>` prints the absolute path to
567 - ``west list`` now prints the manifest repository's path using the
568 ``manifest.path`` :ref:`configuration option <west-config>`, which may differ
569 from the ``self: path:`` value in the manifest data. The old behavior is
570 still available, but requires passing a new ``--manifest-path-from-yaml``
588 - Filter out duplicate extension commands brought in by manifest imports
589 - Fix ``west.Manifest.get_projects()`` when finding the manifest repository by
606 The main user-visible feature in west 0.7 is the :ref:`west-manifest-import`
607 feature. This allows users to load west manifest data from multiple different
608 files, resolving the results into a single logical manifest.
616 <west-manifest-schema-version>`.
624 - The restriction that no project can be named "manifest" is now enforced; the
625 name "manifest" is reserved for the manifest repository, and is usable as
626 such in commands like ``west list manifest``, instead of ``west list
627 path-to-manifest-repository`` being the only way to say that
643 - WestCommand.manifest: this is now settable
649 - west.manifest:
655 - Manifest.as_dict(): new
656 - Manifest.as_frozen_yaml(): new
657 - Manifest.as_yaml(): new
658 - Manifest.from_file() and from_data(): these factory methods are more
660 - Manifest.validate(): new
709 - The :ref:`west manifest <west-built-in-misc>` command also handles errors
713 information which can be read from the manifest file. It still fails if the
725 - west.manifest.Manifest.get_projects(): new
726 - west.manifest.Project.is_cloned(): new
728 Manifest object via a new self.manifest property during the
729 do_run() call. If read, it returns the Manifest object or
731 - west.manifest.Project.git() now has a capture_stderr kwarg
753 - Manifest syntax changes
755 - A west manifest file's ``projects`` elements can now specify their fetch
760 manifest:
773 manifest:
792 manifest:
804 - The command ``west manifest --validate`` can now be run to load and validate
805 the current manifest file, among other error-handling fixes related to
806 manifest parsing.
811 - The ``west.manifest.Project`` constructor's ``remote`` and ``defaults``
816 - ``west.manifest.MANIFEST_SECTIONS`` was removed. There is only one section
817 now, namely ``manifest``. The *sections* kwargs in the
818 ``west.manifest.Manifest`` factory methods and constructor were also
821 - The ``west.manifest.SpecialProject`` class was removed. Use
822 ``west.manifest.ManifestProject`` instead.