Lines Matching full:manifest
12 workspace against the manifest.
14 - Support for a new ``manifest.project-filter`` configuration option.
15 See :ref:`west-config-index` for details. The ``west manifest --freeze``
16 and ``west manifest --resolve`` commands currently cannot be used when
20 warnings. These warnings are errors if the new ``manifest.project-filter``
41 - ``west.manifest.Manifest.is_active()`` now respects the
42 ``manifest.project-filter`` configuration option's value.
49 - Manifest schema version "1.0" is now available for use in this release. This
51 used by applications that do not wish to use a "0.x" manifest "version:"
52 field. See :ref:`west-manifest-schema-version` for details on this feature.
145 open the manifest file instead of dumping stack traces.
149 - The ``west.manifest.MalformedConfig`` exception type has been moved to the
152 - The ``west.manifest.MalformedConfig`` exception type has been moved to the
163 - When calling west.manifest.Manifest.from_file() when outside of a
172 - You can now associate arbitrary user data with the manifest repository
173 itself in the ``manifest: self: userdata:`` value, like so:
177 manifest:
183 - The path to the manifest repository reported by west could be incorrect in
187 ``west.manifest`` API module.
189 - The ``west.Manifest.ManifestProject.__repr__`` return value was fixed
206 - The path handling in the ``west.manifest`` package has been overhauled in a
210 - ``west.manifest.Manifest.validate()``: this now returns the validated data as
214 - ``west.manifest.Manifest``: new:
219 from ``manifest: self: userdata:``, or is None
222 - ``west.manifest.ManifestProject``: new ``userdata`` attribute, which also
223 contains the parsed value from ``manifest: self: userdata:``, or is None
225 - ``west.manifest.ManifestImportFailed``: the constructor can now take any
227 <west-manifest-import-map>` or other compound value.
248 - West manifest files can now contain arbitrary user data associated with each
254 the manifest repository; it now prints ``N/A`` ("not applicable")
259 - The ``west.manifest.Project.userdata`` attribute was added to support
272 - The manifest file parser was incorrectly allowing project names which contain
281 - The changes made in west v0.10.1 to the ``west init --manifest-rev`` option
282 which selected the default branch name were leaving the manifest repository
297 ``west init --manifest-rev`` option value, if given, must now be either a
300 request can no longer be passed to ``--manifest-rev``. Users must now fetch
305 - ``west.manifest.Manifest.get_projects()`` avoids incorrect results in
308 - ``west.manifest.Project.sha()`` now works correctly for tag revisions.
331 avoids issues if the URL changes in the manifest file from when the submodule
337 - the :ref:`west-apis-manifest` module has fixed docstrings for the Project
345 - The :ref:`west-init` command's ``--manifest-rev`` (``--mr``) option no longer
359 <west-manifest-submodules>` is now optional.
363 - West now checks that the manifest schema version is one of the explicitly
364 allowed vlaues documented in :ref:`west-manifest-schema-version`. The old
366 version where the ``manifest: version:`` key was introduced. This incorrectly
371 - A manifest file's ``group-filter`` is now propagated through an ``import``.
373 top level manifest file's ``group-filter`` had any effect; the group filter
379 The new behavior will take effect if ``manifest: version:`` is not given or
381 manifest file only with an explicit ``manifest: version: 0.9``. See
382 :ref:`west-manifest-schema-version` for more information on schema versions.
393 - Commands like ``west manifest --resolve`` now correctly include group and
416 manifest imports is discouraged. The resulting behavior has changed in west
421 - West manifests now support :ref:`west-manifest-submodules`. This allows you
426 - West manifests now support :ref:`west-manifest-groups`. Project groups can be
454 - A manifest file with an empty ``manifest: self: path:`` value is invalid, but
462 - added ``west.manifest.Manifest.is_active()``
463 - added ``west.manifest.Manifest.group_filter``
464 - added ``submodules`` attribute to ``west.manifest.Project``, which has
465 newly added type ``west.manifest.Submodule``
469 - The :ref:`west-manifest-import` feature now supports the terms ``allowlist``
478 This is a feature release which changes the manifest schema by adding support
482 - Manifest import mappings now support a ``path-prefix:`` key, which places
484 See :ref:`west-manifest-ex3.4` for an example.
488 - :ref:`west manifest --path <west-manifest-path>` prints the absolute path to
492 - ``west list`` now prints the manifest repository's path using the
493 ``manifest.path`` :ref:`configuration option <west-config>`, which may differ
494 from the ``self: path:`` value in the manifest data. The old behavior is
495 still available, but requires passing a new ``--manifest-path-from-yaml``
513 - Filter out duplicate extension commands brought in by manifest imports
514 - Fix ``west.Manifest.get_projects()`` when finding the manifest repository by
531 The main user-visible feature in west 0.7 is the :ref:`west-manifest-import`
532 feature. This allows users to load west manifest data from multiple different
533 files, resolving the results into a single logical manifest.
541 <west-manifest-schema-version>`.
549 - The restriction that no project can be named "manifest" is now enforced; the
550 name "manifest" is reserved for the manifest repository, and is usable as
551 such in commands like ``west list manifest``, instead of ``west list
552 path-to-manifest-repository`` being the only way to say that
568 - WestCommand.manifest: this is now settable
574 - west.manifest:
580 - Manifest.as_dict(): new
581 - Manifest.as_frozen_yaml(): new
582 - Manifest.as_yaml(): new
583 - Manifest.from_file() and from_data(): these factory methods are more
585 - Manifest.validate(): new
634 - The :ref:`west manifest <west-built-in-misc>` command also handles errors
638 information which can be read from the manifest file. It still fails if the
650 - west.manifest.Manifest.get_projects(): new
651 - west.manifest.Project.is_cloned(): new
653 Manifest object via a new self.manifest property during the
654 do_run() call. If read, it returns the Manifest object or
656 - west.manifest.Project.git() now has a capture_stderr kwarg
678 - Manifest syntax changes
680 - A west manifest file's ``projects`` elements can now specify their fetch
685 manifest:
698 manifest:
717 manifest:
729 - The command ``west manifest --validate`` can now be run to load and validate
730 the current manifest file, among other error-handling fixes related to
731 manifest parsing.
736 - The ``west.manifest.Project`` constructor's ``remote`` and ``defaults``
741 - ``west.manifest.MANIFEST_SECTIONS`` was removed. There is only one section
742 now, namely ``manifest``. The *sections* kwargs in the
743 ``west.manifest.Manifest`` factory methods and constructor were also
746 - The ``west.manifest.SpecialProject`` class was removed. Use
747 ``west.manifest.ManifestProject`` instead.