| commit | 7fe39afbb6c444f256c1ec0eef008edebcd44644 | [log] [tgz] |
|---|---|---|
| author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Thu Feb 01 12:48:03 2024 +0000 |
| committer | GitHub <noreply@github.com> | Thu Feb 01 12:48:03 2024 +0000 |
| tree | be554b8eb31dfa633aae57a662191d4c707b3373 | |
| parent | d68de5bc53bf33a12334d06748af9db4844d66f0 [diff] |
Bump dart-lang/setup-dart from 1.6.0 to 1.6.2 (#53) Bumps [dart-lang/setup-dart](https://github.com/dart-lang/setup-dart) from 1.6.0 to 1.6.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dart-lang/setup-dart/releases">dart-lang/setup-dart's releases</a>.</em></p> <blockquote> <h2>v1.6.2</h2> <ul> <li>Switch to running the workflow on <code>node20</code> from <code>node16</code>. See also <a href="https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/">Transitioning from Node 16 to Node 20</a>.</li> </ul> <h2>v1.6.1</h2> <ul> <li>Updated the google storage url for <code>main</code> channel releases.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/dart-lang/setup-dart/blob/main/CHANGELOG.md">dart-lang/setup-dart's changelog</a>.</em></p> <blockquote> <h2>v1.6.2</h2> <ul> <li>Switch to running the workflow on <code>node20`` from </code>node16`. See also <a href="https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/">Transitioning from Node 16 to Node 20</a>.</li> </ul> <h2>v1.6.1</h2> <ul> <li>Updated the google storage url for <code>main</code> channel releases.</li> </ul> <h2>v1.6.0</h2> <ul> <li>Enable provisioning of the latest Dart SDK patch release by specifying just the major and minor version (e.g. <code>3.2</code>).</li> </ul> <h2>v1.5.1</h2> <ul> <li>No longer test the <code>setup-dart</code> action on pre-2.12 SDKs.</li> <li>Upgrade JS interop code to use extension types (the new name for inline classes).</li> <li>The upcoming rename of the <code>be</code> channel to <code>main</code> is now supported with forward compatibility that switches when the rename happens.</li> </ul> <h2>v1.5.0</h2> <ul> <li>Re-wrote the implementation of the action into Dart.</li> <li>Auto-detect the platform architecture (<code>x64</code>, <code>ia32</code>, <code>arm</code>, <code>arm64</code>).</li> <li>Improved the caching and download resilience of the sdk.</li> <li>Added a new action output: <code>dart-version</code> - the installed version of the sdk.</li> </ul> <h2>v1.4.0</h2> <ul> <li>Automatically create OIDC token for pub.dev.</li> <li>Add a reusable workflow for publishing.</li> </ul> <h2>v1.3.0</h2> <ul> <li>The install location of the Dart SDK is now available in an environment variable, <code>DART_HOME</code> (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/43">#43</a>).</li> <li>Fixed an issue where cached downloads could lead to unzip issues on self-hosted runners (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/35">#35</a>).</li> </ul> <h2>v1.2.0</h2> <ul> <li>Fixed a path issue impacting git dependencies on Windows.</li> </ul> <h2>v1.1.0</h2> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/dart-lang/setup-dart/commit/fedb1266e91cf51be2fdb382869461a434b920a3"><code>fedb126</code></a> switch to using node20 (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/122">#122</a>)</li> <li><a href="https://github.com/dart-lang/setup-dart/commit/ca7e6fee45ffbd82b555a7ebfc236d2c86439f5b"><code>ca7e6fe</code></a> update the changelog; prep to release 1.6.1 (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/120">#120</a>)</li> <li><a href="https://github.com/dart-lang/setup-dart/commit/c1b2cdbfafc77480d10fe0246ef4dd2f83a9e7b7"><code>c1b2cdb</code></a> Clean up after renaming the be channel to main. (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/115">#115</a>)</li> <li><a href="https://github.com/dart-lang/setup-dart/commit/49b0b8e0a88f72a8fdf1319a41cc261cec63c3c7"><code>49b0b8e</code></a> Bump actions/checkout from 3 to 4 in README.md (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/117">#117</a>)</li> <li><a href="https://github.com/dart-lang/setup-dart/commit/7f54cd0cee53e120db0d1fce4196b7772ebd6f6e"><code>7f54cd0</code></a> Bump <code>@âactions/http-client</code> from 2.1.1 to 2.2.0 (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/112">#112</a>)</li> <li><a href="https://github.com/dart-lang/setup-dart/commit/6e2fe379bd3c8a39facc503f4494396e0de36f13"><code>6e2fe37</code></a> Bump dart-lang/setup-dart from 1.5.1 to 1.6.0 (<a href="https://redirect.github.com/dart-lang/setup-dart/issues/113">#113</a>)</li> <li>See full diff in <a href="https://github.com/dart-lang/setup-dart/compare/b64355ae6ca0b5d484f0106a033dd1388965d06d...fedb1266e91cf51be2fdb382869461a434b920a3">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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`. --- <details> <summary>Dependabot commands and options</summary> <br /> 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>
A package for testing subprocesses.
This exposes a TestProcess class that wraps dart:io's Process class and makes it easy to read standard output line-by-line. TestProcess works the same as Process in many ways, but there are a few major differences.
Process.stdout and Process.stderr are binary streams, which is the most general API but isn‘t the most helpful when working with a program that produces plain text. Instead, TestProcess.stdout and TestProcess.stderr emit a string for each line of output the process produces. What’s more, they're StreamQueues, which means they provide a pull-based API. For example:
import 'package:test/test.dart'; import 'package:test_process/test_process.dart'; void main() { test('pub get gets dependencies', () async { // TestProcess.start() works just like Process.start() from dart:io. var process = await TestProcess.start('dart', ['pub', 'get']); // StreamQueue.next returns the next line emitted on standard out. var firstLine = await process.stdout.next; expect(firstLine, equals('Resolving dependencies...')); // Each call to StreamQueue.next moves one line further. String next; do { next = await process.stdout.next; } while (next != 'Got dependencies!'); // Assert that the process exits with code 0. await process.shouldExit(0); }); }
The test package‘s stream matchers have built-in support for StreamQueues, which makes them perfect for making assertions about a process’s output. We can use this to clean up the previous example:
import 'package:test/test.dart'; import 'package:test_process/test_process.dart'; void main() { test('pub get gets dependencies', () async { var process = await TestProcess.start('dart', ['pub', 'get']); // Each stream matcher will consume as many lines as it matches from a // StreamQueue, and no more, so it's safe to use them in sequence. await expectLater(process.stdout, emits('Resolving dependencies...')); // The emitsThrough matcher matches and consumes any number of lines, as // long as they end with one matching the argument. await expectLater(process.stdout, emitsThrough('Got dependencies!')); await process.shouldExit(0); }); }
If you want to access the standard output streams without consuming any values from the queues, you can use the stdoutStream() and stderrStream() methods. Each time you call one of these, it produces an entirely new stream that replays the corresponding output stream from the beginning, regardless of what's already been produced by stdout, stderr, or other calls to the stream method.
The way signaling works is different from dart:io as well. TestProcess still has a kill() method, but it defaults to SIGKILL on Mac OS and Linux to ensure (as best as possible) that processes die without leaving behind zombies. If you want to send a particular signal (which is unsupported on Windows), you can do so by explicitly calling signal().
In addition to exitCode, which works the same as in dart:io, TestProcess also adds a new method named shouldExit(). This lets tests wait for a process to exit, and (if desired) assert what particular exit code it produced.
When a test using TestProcess fails, it will print all the output produced by that process. This makes it much easier to figure out what went wrong and why. The debugging output uses a header based on the process's invocation by default, but you can pass in custom description parameters to TestProcess.start() to control the headers.
TestProcess will also produce debugging output as the test runs if you pass forwardStdio: true to TestProcess.start(). This can be particularly useful when you're using an interactive debugger and you want to figure out what a process is doing before the test finishes and the normal debugging output is printed.