Greg Spencer 7ab3bc71f9 Be more strict about finding version number attached to a revision. (#28527) ... When we package Flutter, we used to find the "current" tag (which is the version number) by starting at the revision we are building on and looking backwards in time to find the most recent tag. This causes problems on release builds when we failed to tag properly. This PR makes the packaging script be more strict by requiring the given revision to itself have a tag, but only when we're publishing the result. When we're not publishing the result, it's more lenient, since otherwise we couldn't test packaging on non-release commits. I also renamed ProcessRunnerException to PreparePackageException, since we were using that exception more generally than just for processes.		2019-03-01 14:38:40 -08:00
..
analyze-sample-code-test-input	Remove remaining "## Sample code" segments, and fix the snippet generator. (#27793)	2019-02-15 07:48:49 -08:00
analyze-sample-code_test.dart	Remove remaining "## Sample code" segments, and fix the snippet generator. (#27793)	2019-02-15 07:48:49 -08:00
common.dart	Revert "Remove package:test dependency from flutter_test (#23755)" (#24004)	2018-11-06 09:12:48 -08:00
fake_process_manager_test.dart	Add missing trailing commas (#28673)	2019-03-01 08:17:55 +01:00
fake_process_manager.dart	Add missing trailing commas (#28673)	2019-03-01 08:17:55 +01:00
prepare_package_test.dart	Be more strict about finding version number attached to a revision. (#28527)	2019-03-01 14:38:40 -08:00