Closed renovate[bot] closed 3 months ago
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
Too many breaking changes. Address later.
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x
releases. But if you manually upgrade to 4.x
then Renovate will re-enable minor
and patch
updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
^3.3.1
->^4.0.0
Release Notes
GoogleChrome/web-vitals (web-vitals)
### [`v4.1.1`](https://togithub.com/GoogleChrome/web-vitals/blob/HEAD/CHANGELOG.md#v411-2024-06-10) [Compare Source](https://togithub.com/GoogleChrome/web-vitals/compare/v4.1.0...v4.1.1) - Fix pending LoAF cleanup logic ([#493](https://togithub.com/GoogleChrome/web-vitals/pull/493)) ### [`v4.1.0`](https://togithub.com/GoogleChrome/web-vitals/blob/HEAD/CHANGELOG.md#v410-2024-06-06) [Compare Source](https://togithub.com/GoogleChrome/web-vitals/compare/v4.0.1...v4.1.0) - Move the support check to the top of the onINP() function ([#490](https://togithub.com/GoogleChrome/web-vitals/pull/490)) - Fix missing LoAF attribution when entries are dispatched before event entries ([#487](https://togithub.com/GoogleChrome/web-vitals/pull/487)) ### [`v4.0.1`](https://togithub.com/GoogleChrome/web-vitals/blob/HEAD/CHANGELOG.md#v401-2024-05-21) [Compare Source](https://togithub.com/GoogleChrome/web-vitals/compare/v4.0.0...v4.0.1) - Add the `ReportCallback` type back but deprecate it ([#483](https://togithub.com/GoogleChrome/web-vitals/pull/483)) ### [`v4.0.0`](https://togithub.com/GoogleChrome/web-vitals/blob/HEAD/CHANGELOG.md#v400-2024-05-13) [Compare Source](https://togithub.com/GoogleChrome/web-vitals/compare/v3.5.2...v4.0.0) - **\[BREAKING]** Update types to support more generic usage ([#471](https://togithub.com/GoogleChrome/web-vitals/pull/471)) - **\[BREAKING]** Split `waitingDuration` to make it easier to understand redirect delays ([#458](https://togithub.com/GoogleChrome/web-vitals/pull/458)) - **\[BREAKING]** Rename `TTFBAttribution` fields from `*Time` to `*Duration` ([#453](https://togithub.com/GoogleChrome/web-vitals/pull/453)) - **\[BREAKING]** Rename `resourceLoadTime` to `resourceLoadDuration` in LCP attribution ([#450](https://togithub.com/GoogleChrome/web-vitals/pull/450)) - **\[BREAKING]** Add INP breakdown timings and LoAF attribution ([#442](https://togithub.com/GoogleChrome/web-vitals/pull/442)) - **\[BREAKING]** Deprecate `onFID()` and remove previously deprecated APIs ([#435](https://togithub.com/GoogleChrome/web-vitals/pull/435)) - Expose the target element in INP attribution ([#479](https://togithub.com/GoogleChrome/web-vitals/pull/479)) - Save INP target after interactions to reduce null values when removed from the DOM ([#477](https://togithub.com/GoogleChrome/web-vitals/pull/477)) - Cap TTFB in attribution ([#440](https://togithub.com/GoogleChrome/web-vitals/pull/440)) - Fix `reportAllChanges` behavior for LCP when library is loaded late ([#468](https://togithub.com/GoogleChrome/web-vitals/pull/468)) ### [`v3.5.2`](https://togithub.com/GoogleChrome/web-vitals/blob/HEAD/CHANGELOG.md#v352-2024-01-25) [Compare Source](https://togithub.com/GoogleChrome/web-vitals/compare/v3.5.1...v3.5.2) - Pick the first non-null `target` for INP attribution ([#421](https://togithub.com/GoogleChrome/web-vitals/pull/421))Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: