chore(deps): update dependency @fastify/middie to v8.3.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@fastify/middie	8.3.1 -> 8.3.3

---

Release Notes

fastify/middie (@​fastify/middie)

v8.3.3

Compare Source

Security

• path-to-regexp is updated to 6.3.0 to prevent ReDOS attack, it is recommended to use the latest version of this package.

What's Changed

• fix(8.x): use path-to-regexp@6.3.0 by @​climba03003 in https://github.com/fastify/middie/pull/215

Full Changelog: fastify/middie@v8.3.2...v8.3.3

v8.3.2

Compare Source

Deprecated

This version includes too much breaking change due to security patch. Please upgrade to version 8.3.3 which includes the security patch with minimal breakages.

Security

• path-to-regexp is updated to 8.1.0 to prevent ReDOS attack, it is recommended to use the latest version of this package.

You may see some unexpected breaking due the security patch. Here is the workaround,

1. when you are using wildcard *, you must to provides a param name.

// before
fastify.use('*.css')
// after
fastify.use('*filename{.css}')

What's Changed

• chore(8.x): bump path-to-regexp to 8.1.0 by @​climba03003 in https://github.com/fastify/middie/pull/213

Full Changelog: fastify/middie@v8.3.1...v8.3.2

---

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 could not resolve
npm error
npm error While resolving: sinon-chai@4.0.0
npm error Found: chai@4.5.0
npm error node_modules/chai
npm error   dev chai@"4.5.0" from the root project
npm error   peer chai@">= 2.1.2 < 6" from chai-as-promised@7.1.2
npm error   node_modules/chai-as-promised
npm error     dev chai-as-promised@"7.1.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@"^5.0.0" from sinon-chai@4.0.0
npm error node_modules/sinon-chai
npm error   dev sinon-chai@"4.0.0" from the root project
npm error
npm error Conflicting peer dependency: chai@5.1.2
npm error node_modules/chai
npm error   peer chai@"^5.0.0" from sinon-chai@4.0.0
npm error   node_modules/sinon-chai
npm error     dev sinon-chai@"4.0.0" 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-11-18T08_53_24_146Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-18T08_53_24_146Z-debug-0.log