[roll] Roll infra/recipes [snap_branch] Report versioning history to an...

...upstream versioning server.

We'll send out separate cls accounting for the other recipes that create
release branches (i.e. `cherry_pick`, `create_branch`, and
`increment_version`) at a later date.
For now, only canary releases (created via `snap_branch`) are integrated
into android; that is why we're updating this recipe first.

`api.artifact_versioning.register_versioning` also now accepts `str`
instead of `ReleaseVersion` since android artifact versions won't use
`ReleaseVersion`, and we'll need to eventually support those.

Original-Bug: 422540705
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/infra/recipes/+/1342944
Original-Revision: 393079bb93b69cddf96a47745c0d4e78dc411d72
GitOrigin-RevId: 7db2c68b2d28036c50fcdcfac4c85afe2693933a
Change-Id: I1b94680ab98752b1126a9deff9225369f0437fee
1 file changed
tree: dbed725070423385e0a02d1bcf7db2984563fc98
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.