• Greg Spencer's avatar
    Be more strict about finding version number attached to a revision. (#28527) · 7ab3bc71
    Greg Spencer authored
    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.
    7ab3bc71
Name
Last commit
Last update
..
automated_tests Loading commit data...
benchmarks Loading commit data...
bots Loading commit data...
ci Loading commit data...
devicelab Loading commit data...
docs Loading commit data...
integration_tests Loading commit data...
manual_tests Loading commit data...
missing_dependency_tests Loading commit data...
snippets Loading commit data...
tools Loading commit data...
README.md Loading commit data...