Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(deps): Bump web-vitals from 4.2.2 to 4.2.3 (#191)
Bumps [web-vitals](https://github.com/GoogleChrome/web-vitals) from 4.2.2 to 4.2.3. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/GoogleChrome/web-vitals/blob/main/CHANGELOG.md">web-vitals's changelog</a>.</em></p> <blockquote> <h3>v4.2.3 (2024-08-06)</h3> <ul> <li>Fix missing LoAF entries in INP attribution (<a href="https://redirect.github.com/GoogleChrome/web-vitals/pull/512">#512</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/GoogleChrome/web-vitals/commit/9b932519b16f72328c6d8e9814b811f1bc1a0bb5"><code>9b93251</code></a> Release v4.2.3</li> <li><a href="https://github.com/GoogleChrome/web-vitals/commit/6cb4f930370b5cdb90820986ddeef049e0db6856"><code>6cb4f93</code></a> Update CHANGELOG</li> <li><a href="https://github.com/GoogleChrome/web-vitals/commit/8cdceaf90b125b2946b20f0d54fba88150f89ffa"><code>8cdceaf</code></a> INP attribution: ensure LoAF order is maintained (<a href="https://redirect.github.com/GoogleChrome/web-vitals/issues/512">#512</a>)</li> <li><a href="https://github.com/GoogleChrome/web-vitals/commit/5b91b766031c435e44dda912be75f685d77fe073"><code>5b91b76</code></a> Improve test flakiness (<a href="https://redirect.github.com/GoogleChrome/web-vitals/issues/507">#507</a>)</li> <li>See full diff in <a href="https://github.com/GoogleChrome/web-vitals/compare/v4.2.2...v4.2.3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=web-vitals&package-manager=npm_and_yarn&previous-version=4.2.2&new-version=4.2.3)](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 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> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information