[roll] Roll fuchsia [bazel_sdk] fix analysis failure in fuchsia_api_level

This CL adds the ability to use the flag that we define for pigweed
which skips fuchsia targets to opt out of the analysis failures that
occur when we have an unset api level. This happens because in pigweed
they run builds with `bazel build //...` which ends up running the
implementation of the fuchsia_api_level rule to figure out what the
build config value should be. We cannot avoid running this implementation
so we use the flag they already have set to skip validation.

Original-bug: 354047162
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1173506
Original-Revision: 1747704cf2b00fcf64c29e63cf3a59a00601d091
GitOrigin-RevId: f64cb901b8fa41a8a9eabcfbf5862697cd3fccd0
Change-Id: I44207a7ab870edb3271195d1ab17b417dc280160
1 file changed
tree: dbc5143f3012bd19b86c82fb8ea1afb352111a25
  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.