[roll] Roll fuchsia [logs] Remove explicit shard reference in RealmBuilder shard

The RealmBuilder shard is shipped in the SDK.
SDK consumers may want custom routing for LogSink
and InspectSink. Forcing them to include the shard
removes a lot of flexibility, and makes migrations
of LogSink routing more difficult, not simpler.
All out-of-tree users have migrated to explicit
routes or explicit dependencies on the LogSink shard,
so it's safe to update this.

Original-Fixed: 404543928
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1258026
Original-Revision: 808411b3edeedbae97ca763a1f11d158356d07ce
GitOrigin-RevId: 2b4a7d240641ee496ff2d9f7c5cb5db298266b8b
Change-Id: I6a01fd29ce9a63e51e4c66c36e7c80bf200986d1
1 file changed
tree: 68b99d60c5f3e9af85f9d6a02b2e19fa14fb3387
  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.