[roll] Roll fuchsia [assembly] Set release version during config generation.

This cleans up the logic that sets the "release_version" field in
board_configs and board_input_bundles. Build rules can set the values
explicitly in GN or Bazel targets, but the config generator tool will
set the default value "unversioned" if no value is provided.

This also allows targets to set these versions as a string directly in
the target, or as a path to a file somewhere in their workspace. This is
necessary to support some board definitions in other repositories.

Original-Bug: b/399808455
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1238429
Original-Revision: 4077eaa2afb94144c002d6e1d8187a05a780c317
GitOrigin-RevId: 68542562eb57c8aaea65e3f730b3b7d8efc867a3
Change-Id: I1c9458c6fb9a11af4122e4c5f14b75e14312e8ed
1 file changed
tree: a6ce92d7f59180b60ec4b69c46f707062c917799
  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.