Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2024

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package Change Age Confidence
pretty-quick 3.1.3 -> 3.3.1 age confidence

Release Notes

prettier/pretty-quick (pretty-quick)

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes
  • #​180 93924ab Thanks @​SukkaW! - refactor: replace chalk and multimatch with their lightweight and performant alternatives
Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes

v3.1.4

Compare Source

Patch Changes

Configuration

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

🚦 Automerge: Enabled.

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.


  • 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 1, 2024

⚠ 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/prettier
npm error   dev prettier@"3.2.5" from the root project
npm error
npm error Could not resolve dependency:
npm error peer prettier@"^2.0.0" from [email protected]
npm error node_modules/pretty-quick
npm error   dev pretty-quick@"3.3.1" 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 /tmp/renovate/cache/others/npm/_logs/2024-05-01T06_38_22_962Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-01T06_38_22_962Z-debug-0.log

@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from 59a21fa to 951e68b Compare April 1, 2024 10:16
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from 5771d9f to ee0b76e Compare May 1, 2024 06:38
Copy link
Contributor Author

renovate bot commented Jun 1, 2024

⚠️ 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 unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/prettier
npm error   dev prettier@"3.4.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer prettier@"^2.0.0" from [email protected]
npm error node_modules/pretty-quick
npm error   dev pretty-quick@"3.3.1" 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-08-31T10_44_41_082Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-31T10_44_41_082Z-debug-0.log

@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from b14c8e5 to 3ee1b46 Compare June 1, 2024 09:07
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 4 times, most recently from 4ea21cd to a2b89d6 Compare July 1, 2024 12:37
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from bef08f3 to 42f39af Compare August 1, 2024 07:36
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from 6db16bd to 92a1d66 Compare September 1, 2024 06:43
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 4 times, most recently from 21c6d2d to f456685 Compare October 1, 2024 12:27
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from 46173e8 to 656952a Compare December 1, 2024 21:16
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 4 times, most recently from 5019b58 to b8b75e2 Compare January 1, 2025 13:14
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch 2 times, most recently from 53c6b27 to 7fd5255 Compare February 1, 2025 08:25
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch from 7fd5255 to 00ceee5 Compare March 1, 2025 05:21
@renovate renovate bot force-pushed the renovate/pretty-quick-3.x branch from 00ceee5 to 9b2a3fa Compare March 1, 2025 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants