[roll] Roll fuchsia [routing] wire up expose to framework

We already allow "expose to framework" in our manifests, and after
talking with Olivia it sounds like it would be a useful way for a
component to signify that it has a protocol that it wants component
manager to access.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1183812
Original-Revision: 11ce1a12c12df5f151afd8c61acdc2c3820810d9
GitOrigin-RevId: 95cda53bf5e4e119814545fcde9a0caf8e48a1a2
Change-Id: I9e134a311a725fba2bd86bc8f5bec5857e5ea41d
1 file changed
tree: 18ea7934012d4962f15d913eb73e80a5ffbddcf1
  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.