Add optional rel_hash property to release_publish.

This would allow us to define a specific commit to publish as a tagged
release, instead of the (default) inferred latest commit in a branch; it
is likely use would be rarer but would still allow a way for us to either
publish a specific commit, or intentionally publish an older commit.

See https://github.com/flutter/flutter/issues/170547.

Change-Id: Idab39c8e53c0a98a904c9989fbbcb3038b9916b9
Bug: https://github.com/flutter/flutter/issues/170547
Reviewed-on: https://flutter-review.googlesource.com/c/recipes/+/66662
Reviewed-by: Jason Simmons <jsimmons@google.com>
Commit-Queue: Matan Lurey <matanl@google.com>
2 files changed
tree: 96c9bd75d1b1dfa51ee2cc82568c00e6aa50067c
  1. .vscode/
  2. infra/
  3. recipe_modules/
  4. recipes/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. CONTRIBUTING.md
  9. LICENSE
  10. OWNERS
  11. README.md
  12. recipes.py
README.md

Flutter LUCI Recipes

This repository contains Flutter's LUCI recipes. For the LUCI infrastructure config, see flutter/infra. Builds can be found in the Flutter Dashboard.

Supported repositories roll their .ci.yaml into flutter/infra, which updates what properties builds have. For example, flutter config specifies various dependencies the different tests require, which are then used by the flutter_deps recipe_module No modifications to flutter/infra are required to work on the recipes.

Contributing

Please follow instructions on Contributing docs to set up your development environment.