[roll] Roll fuchsia Revert "[versioning] Assert a valid API level has been specified" This reverts commit 56e9e30f8bb5ea3cca30df465914304413536f4e. Reason for revert: Breaks the toolchain build because it does not specify an API level but includes this file via fdio, at least. Example failure: http://ci.chromium.org/b/8754806295409845249 Original change's description: > [versioning] Assert a valid API level has been specified > > Previously, `availability` attributes would only be added if > `__Fuchsia_API_level__` is defined, but there was no guarantee in the > file that it is always defined when targeting Fuchsia or set to a valid > value. Add such a check and comments about why it must be defined. > > Original-Bug: 42085580 > Test: fx build && fx build final_fuchsia_idk > Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/942773 Original-Bug: 42085580 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/999700 Original-Revision: aee84b78210c3c5e3e2118184f63c835c05371ad GitOrigin-RevId: 5c195cec8b861426fcf6024d47b07c98f1faba07 Change-Id: Ieb4c8adcf938d5decd695bcf603f439cc46eea98
This repository contains Fuchsia's Global Integration manifest files.
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 via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.