* Use pub deps in go_router_builder
* use make-deps-path-based in analyze steps
* remove newline
* add make-deps-path-based for tests
* Cause go_router_builder to break, but go_router tests pass
* (test) bump go_router to 4.0.1
* Revert experimental breakage
* Revert go_router to 4.0.0
* Specify go_router_builder version in pubspec
* bump go_router_builder version
* Use path dependency overrides in example
* remove dependency overrides - unsupported by make-deps-path-based
* update go_router_builder/CHANGELOG.md
* Change go_router_builder/example pubspec to point to pub.dev
* Add separate pathified_* checks
* Update go_router_builder SDK constraints
Specify the same SDK constraints as go_router in go_router_builder
* Use path-based dependency for go_router_builder in example
* Address code review comments
* add --run-on-dirty-packages to pathified test script
* Use --run-on-changed-packages flag for analyze
* Bypass tool_runner.sh to use --run-on-dirty-packages flag
The tool_runner.sh script adds the "--packages-for-branch" flag,
which can't be used with "--run-on-dirty-packages flag"
https://github.com/flutter/packages/blob/main/script/tool_runner.sh#L12
* Remove unused _go_router_fake package
* Format .cirrus.yml, use a shared dart_unit_tests_exceptions.yaml file
* Remove redundant comment
* Update CHANGELOG.md
* Update .cirrus.yml
* Added new names for events:
* isBeginFrame: "WebFrameWidgetImpl::BeginMainFrame"
* isUpdateAllLifecyclePhases: "WebFrameWidgetImpl::UpdateLifecycle"
* Testing:
* Add browser.dart unit tests and testing information.
* Add test matrix to run the benchmark in Chromium 84 and 98.
Co-authored-by: David Iglesias Teixeira <ditman@gmail.com>
Updates tool pin to 0.7.3
- Enables versiond and CHANGELOG update checks.
- Enables timing logging.
Changes to allow the roll to pass:
- Adds missing licenses to Kotlin files (which were not previously checked).
- Adds missing AUTHORS files.
- Adjusts package descriptions to meet pub.dev length guidelines, which the tooling now enforces.
Picks up 0.6.0+1 of the tool, which among other things fixes `build-examples` to run on non-plugin packages.
Related changes:
- Simplifies tool_runner.sh using new tool flag, to match the recent change to flutter/plugins.
- Disables sharding of the build+native test tasks; even with building now working again, it's clear there's not enough load to warrant the shards; each one has about 1 minute of setup, and then the build times per shard varied from 1-4 minutes. Using an extra machine to run in 1+1 and 1+4 minutes is not a win over just doing a single 1+5 minute run.
Rolls to the latest release of flutter_plugin_tools, updating calls for breaking changes to flags.
Other minor changes:
- Removes the default set of actions from `tool_runner.sh` since it's never used, and the set of things it runs is a very obsolete subset at this point; it's better to require people to choose specific actions.
- Renames some tasks to match recent renaming in flutter/plugins.
Updates to better align with the current flutter/plugins tooling:
- Pulls the latest flutter_plugin_tools
- Enables the new version-check functionality
- Enables the new license-check functionality
- Switches over to the new publish check functionality
- Moves format checking to a bot that does several of the very fast
checks, leaving tests as their own bot
- Switches incremental_build.sh to use the new --run-on-changed-packages
functionality instead of the bash check_changed_packages
- Moves check_changed_packages into local_tests.sh to minimize the
chances of future new code trying to use it, as it is now legacy.
- Renames incremental_build.sh to tool_runner.sh, to better match its
current behavior/use
Allows publishing NNBD packages as stable previews rather than prereleases without CI being red. The step still runs, so it can be manually validated for other issues. Since this repository is low-traffic, and the cost of something slipping through here is minor (since it will be caught when actually trying to publish), it's not worth engineering a solution to ignore only the specific failure in this case.
This should be reverted once NNBD support is on stable.
