Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 20, 2025

This PR contains the following updates:

Package Change Age Confidence
globals 15.14.0 -> 16.4.0 age confidence

Release Notes

sindresorhus/globals (globals)

v16.4.0

Compare Source

v16.3.0

Compare Source


v16.2.0

Compare Source


v16.1.0

Compare Source


v16.0.0

Compare Source

Breaking
  • The serviceworker globals are now generated from browsers (#​281) 039ed51
    • It's a breaking change as a few globals have been removed.

v15.15.0

Compare Source



Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Apr 27, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @types/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/chai
npm error   dev @types/chai@"5.2.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @types/chai@"<5.2.0" from @types/[email protected]
npm error node_modules/@types/chai-subset
npm error   dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/chai
npm error   peer @types/chai@"<5.2.0" from @types/[email protected]
npm error   node_modules/@types/chai-subset
npm error     dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-09-09T20_31_19_270Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-09T20_31_19_270Z-debug-0.log

@renovate renovate bot force-pushed the renovate/globals-16.x branch from 6d73ade to f06dc06 Compare April 27, 2025 02:14
@renovate renovate bot force-pushed the renovate/globals-16.x branch from f06dc06 to aeadfb2 Compare May 7, 2025 13:37
@renovate renovate bot force-pushed the renovate/globals-16.x branch 2 times, most recently from a97bfe9 to c7a6aca Compare May 25, 2025 22:55
@renovate renovate bot force-pushed the renovate/globals-16.x branch from c7a6aca to 1863e79 Compare July 12, 2025 16:01
@renovate renovate bot force-pushed the renovate/globals-16.x branch 2 times, most recently from 4f56812 to 633458a Compare August 13, 2025 12:00
@renovate renovate bot force-pushed the renovate/globals-16.x branch from 633458a to 3dc0565 Compare August 23, 2025 15:59
@renovate renovate bot force-pushed the renovate/globals-16.x branch from 3dc0565 to d082c0e Compare August 31, 2025 09:52
@renovate renovate bot force-pushed the renovate/globals-16.x branch from d082c0e to caca836 Compare September 9, 2025 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

0 participants