## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [ ] All existing and new tests are passing.
---------
Co-authored-by: David Iglesias <ditman@gmail.com>
Co-authored-by: Mark Thompson <2554588+MarkTechson@users.noreply.github.com>
Co-authored-by: John Ryan <ryjohn@google.com>
Bumps [jasmine-core](https://github.com/jasmine/jasmine) from 4.5.0 to
4.6.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/jasmine/jasmine/releases">jasmine-core's
releases</a>.</em></p>
<blockquote>
<h2>4.6.0</h2>
<p>Please see the <a
href="https://github.com/jasmine/jasmine/blob/main/release_notes/4.6.0.md">release
notes</a>.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="f509078020"><code>f509078</code></a>
Bump version to 4.6.0</li>
<li><a
href="ff237f4b66"><code>ff237f4</code></a>
Fixed sass version pinning</li>
<li><a
href="e42e3d9e00"><code>e42e3d9</code></a>
Pin sass to the last version that works on Node 12</li>
<li><a
href="166e5f4d6c"><code>166e5f4</code></a>
Report the ID of each suite/spec's parent</li>
<li><a
href="6ad8d20694"><code>6ad8d20</code></a>
Report the path/url of the file that the spec/suite was defined in</li>
<li><a
href="bc3a495160"><code>bc3a495</code></a>
Pin eslint-plugin-compat to <4.1.0 to fix import error on CI</li>
<li><a
href="b323631611"><code>b323631</code></a>
Pin Grunt to <1.6.0 for compatiblity with Node 12</li>
<li><a
href="e8767ba660"><code>e8767ba</code></a>
Removed "Does the problem occur with the latest version of
jasmine-core" from...</li>
<li><a
href="169a2a8ad2"><code>169a2a8</code></a>
Upgraded to new issue templates</li>
<li><a
href="b267029301"><code>b267029</code></a>
Revert "Upgraded to new issue templates"</li>
<li>Additional commits viewable in <a
href="https://github.com/jasmine/jasmine/compare/v4.5.0...v4.6.0">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`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<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 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>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [karma](https://github.com/karma-runner/karma) from 6.4.1 to
6.4.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/karma-runner/karma/releases">karma's
releases</a>.</em></p>
<blockquote>
<h2>v6.4.2</h2>
<h2><a
href="https://github.com/karma-runner/karma/compare/v6.4.1...v6.4.2">6.4.2</a>
(2023-04-21)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>few typos (<a
href="c6a42710b4">c6a4271</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/karma-runner/karma/blob/master/CHANGELOG.md">karma's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/karma-runner/karma/compare/v6.4.1...v6.4.2">6.4.2</a>
(2023-04-21)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>few typos (<a
href="c6a42710b4">c6a4271</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="9de3c00988"><code>9de3c00</code></a>
chore(release): 6.4.2 [skip ci]</li>
<li><a
href="c6a42710b4"><code>c6a4271</code></a>
fix: few typos</li>
<li><a
href="50f963551f"><code>50f9635</code></a>
docs: update codeclimate badge in readme.md</li>
<li>See full diff in <a
href="https://github.com/karma-runner/karma/compare/v6.4.1...v6.4.2">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`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<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 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>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
## Pre-launch Checklist
- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-devrel
channel on [Discord].
<!-- Links -->
[Flutter Style Guide]:
https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
[CLA]: https://cla.developers.google.com/
[Discord]: https://github.com/flutter/flutter/wiki/Chat
[Contributors Guide]:
https://github.com/flutter/samples/blob/main/CONTRIBUTING.md
Co-authored-by: Mark Thompson
<2554588+MarkTechson@users.noreply.github.com>
Co-authored-by: David Iglesias <ditman@gmail.com>
Co-authored-by: Mark Thompson <2554588+MarkTechson@users.noreply.github.com>
Co-authored-by: David Iglesias <ditman@gmail.com>
Parker Lougheed
dependabot[bot]
Brett Morgan
David Iglesias