chore(deps): update dependency pretty-quick to v3

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pretty-quick	1.11.1 -> 3.1.3

---

Release Notes

azz/pretty-quick

v3.1.3

Compare Source

Bug Fixes

• detect git when in use git worktree (#​142) (bc231a3)

v3.1.2

Compare Source

Bug Fixes

• check for supportedExtenions after filtering ignored files (#​143) (5cb47e6)

v3.1.1

Compare Source

Bug Fixes

• allow non-core file extensions (from plugins) (#​128) (262a02d)

v3.1.0

Compare Source

Features

• add an --ignore-path flag (#​115) (eaf29e2)

v3.0.2

Compare Source

Bug Fixes

• don't ignore file extensions defined in .prettierrc overrides (#​111) (30699de)

v3.0.1

Compare Source

Bug Fixes

• don't copy tests on build (#​112) (e500e3c)

v3.0.0

Compare Source

• BREAKING CHANGE: require node 10 and prettier 2 (#​104) (9290ae4), closes #​104

BREAKING CHANGES

• Node >=10.13.0 is required
• Prettier ^2.0.0 is required

If you are still on an older version of Node, or using Prettier v1, please stay on pretty-quick@2.

Other Changes

• Run Prettier on full codebase

v2.0.2

Compare Source

2.0.2 (2020-08-21)

Bug Fixes

• allow .js.flow extension (#​103) (5360691), closes /github.com/prettier/prettier/blob/ef880ec4b93230ac1c45be830ff060e78e0740d8/src/language-js/index.js#L22

v2.0.1

Compare Source

2.0.1 (2019-11-05)

Bug Fixes

• handling of submodules and .git path (#​90) (#​92) (3370668)

v2.0.0

Compare Source

Bug Fixes

• upgrade dependencies (#​85) (116f248)

BREAKING CHANGES

• requires node 8

---

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, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel[bot]]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/notrab/commerceql/g9qxt94s4
✅ Preview: https://commerceql-git-renovate-pretty-quick-3x.notrab.vercel.app

[renovate[bot]]

:warning: Artifact update problem

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

:recycle: 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 check 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 old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: commerceql-boilerplate@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/prettier
npm ERR!   dev prettier@"1.19.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer prettier@">=2.0.0" from [email protected]
npm ERR! node_modules/pretty-quick
npm ERR!   dev pretty-quick@"3.1.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-02-02T21_04_07_795Z-debug.log

[vercel[bot]]

Deployment failed with the following error:

should NOT have additional property `dotenv`

[renovate[bot]]

⚠ 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 old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: commerceql-boilerplate@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/prettier
npm ERR!   dev prettier@"1.19.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer prettier@">=2.0.0" from [email protected]
npm ERR! node_modules/pretty-quick
npm ERR!   dev pretty-quick@"3.1.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-20T12_56_15_483Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-20T12_56_15_483Z-debug-0.log