commit | d2e363474bb08602c934335d3d80f22c65cc6f8c | [log] [tgz] |
---|---|---|
author | Matan Lurey <matanl@google.com> | Mon Jun 16 16:47:25 2025 -0700 |
committer | CQ Bot Account <flutter-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 16 16:47:25 2025 -0700 |
tree | 96c9bd75d1b1dfa51ee2cc82568c00e6aa50067c | |
parent | 768c3a0e928b8c553656419eebb048984794d3e3 [diff] |
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>
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.
Please follow instructions on Contributing docs to set up your development environment.