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

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pretty-quick	3.1.3 → 3.3.1

---

Release Notes

prettier/pretty-quick (pretty-quick)

v3.3.1

Compare Source

Patch Changes

• #​185 ca4d269 Thanks @​JounQin! - fix: remove unexpected .tsbuildinfo file

v3.3.0

Compare Source

Minor Changes

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

Patch Changes

• #​183 71aab56 Thanks @​JounQin! - fix: more robust computation of git directory

v3.2.1

Compare Source

Patch Changes

• #​178 1929cc9 Thanks @​JounQin! - fix: add tslib as dependency

v3.2.0

Compare Source

Minor Changes

• #​175 4f5a345 Thanks @​JounQin! - feat: migrate code base to TypeScript

v3.1.4

Compare Source

Patch Changes

• #​172 49acad2 Thanks @​JounQin! - fix: incorrect prettier peer version

---

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.

[renovate]

⚠ 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: node-aws-lambda-example-hello-world@0.0.0
npm error Found: prettier@3.2.5
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 pretty-quick@3.3.1
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-01T10_23_13_319Z-eresolve-report.txt

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

[renovate]

⚠️ 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: node-aws-lambda-example-hello-world@0.0.0
npm error Found: prettier@3.4.2
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 pretty-quick@3.3.1
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/2026-02-02T14_48_03_948Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T14_48_03_948Z-debug-0.log