[roll] Roll fuchsia [assembly] Fix component shards in compiled packages for assembly overrides

This fixes the addition of component shards for compiled packages and
components in assembly developer overrides for assembly targets in GN
and Bazel both.

It also marks attempting to add 'contents' or 'component_includes' as
errors as they are not currently supported for Bazel-based assembly
targets (some big refactoring needs to happen to support them).

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1238665
Original-Revision: 6dfc931e8fa2e87e32d5654e892e85103d3c8cef
GitOrigin-RevId: 942153c6eeee431f7de492cc37a620168e623f6a
Change-Id: I0b8a3e4df1bf1c757fcc74b440a872f7d91f4872
1 file changed
tree: bfdb7082713150eca44969899d71201a9548ecab
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.