mirror of https://github.com/flutter/samples.git
Bump jasmine-core from 4.5.0 to 4.6.0 in /web_embedding/ng-flutter (#1785)
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="pull/1801/headf509078020
"><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 /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=jasmine-core&package-manager=npm_and_yarn&previous-version=4.5.0&new-version=4.6.0)](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>
parent
27ce882a04
commit
474756ce04
Loading…
Reference in new issue