[dependabot]

Bumps the dev-dependencies group with 2 updates: build_runner and test.

Updates build_runner from 2.16.1 to 2.16.2

Release notes

Sourced from build_runner's releases.

package:build_runner v2.16.2

• Support analyzer 14.5.0. Require analyzer 14.3.0.

Commits

• 520fec4 Release build_runner 2.16.2 and build_test 3.5.21: support analyzer 14.5.0. (...
• See full diff in compare view

Updates test from 1.31.1 to 1.32.0

Release notes

Sourced from test's releases.

package:test v1.32.0

• Precompiled browser tests: stop serving files from outside the precompiled root directory. The static handler no longer sets serveFilesOutsidePath, restoring path-containment parity with the dart2js and dart2wasm compilers.
• Export TestFailure from package:test/scaffolding.dart.
• Support --compiler cli with the vm-asan, vm-msan, and vm-tsan runtimes.
• Add support for DART_TEST_REPORTER environment variable in test runner and when tests are run directly on platforms which support dart:io. The environment variable takes precedence over configuration in dart_test.yaml but is overridden by the --reporter flag when passed to the test runner.
• Suppress dart2js compiler output for successful compiles.
• Include output from passing tests messages within the Passing tests group in GithubReporter.
• Only include VM debugger in output when using interactive debugging, suppress it when only using coverage.
• Use a redirect html file for browser tests to avoid leaking websocket details through process starting arguments.
• Migrate out of process VM tests communication channel from TCP sockets to Unix domain sockets inside a restricted temporary directory.
• Pass Node.js test process connection configuration and secret token via a restricted temporary authentication file to prevent secret leakage in command line process arguments.
• Enable asserts in the exe compiler.
• Keep the CHROME_EXECUTABLE, MS_EDGE_EXECUTABLE, FIREFOX_EXECUTABLE, and SAFARI_EXECUTABLE overrides working when the browser is also configured through override_platforms or define_platforms. Any setting on those platforms used to drop the variable.
• Fix race conditions in Chrome coverage collection where tests could finish before DevTools connection and coverage profiling were initialized.
• Fix deadlock that may occur running tests with the exe compiler.

package:test v1.31.2

• Add support for running tests as native CLI bundles (vm platform only).
  • You can run tests this way with --compiler cli.
• Impacts Configuration Support using the OS platform selector to configure browser tests. Previously tests loaded for the browser would have an operating system of "none", now they will have an operating system matching the system the browser is running on. This allows more specific configuration, such as skipping a particular browser test on a particular platform. This may impact existing configuration which relied on the configuration for browser tests being independent from any OS specific configuration. For instance a wide skip of all tests with OS 'windows' would previously still run browser tests on windows, but will now skip all tests including browser tests.
• Use a DevTools URL instead of a defunct observatory URL.
• Disable throttling in chrome launch arguments.
• Allow package_config 3.x.x.
• Require analyzer: '>=13.0.0 <15.0.0'
• Use the compact or failures-only reporters by default for tests run directly

... (truncated)

Commits

• 6783445 Prepare to publish (#2737)
• 575e4da Fix deadlock waiting on serverSocket (#2740)
• bd9acf3 Unskip a test on windows (#2741)
• b575eda Remove redundant tag (#2738)
• 73e85f1 Precompiled browser tests: stop serving files from outside the precompiled ro...
• bbe8f9b Export TestFailure from package:test_api/scaffolding.dart (#2723)
• 55b186d Fix race conditions in Chrome coverage collection (#2715)
• 51463b0 Keep the browser executable env override through a settings merge (#2722)
• b87a249 Enable asserts (#2719)
• dd426d4 Obfuscate the test runner connection for VM and Node tests (#2704)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions