fix(deps): update middy-js monorepo to v6 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@middy/core (source)	5.5.1 -> 6.0.0
@middy/error-logger (source)	5.5.1 -> 6.0.0
@middy/http-content-negotiation (source)	5.5.1 -> 6.0.0
@middy/http-error-handler (source)	5.5.1 -> 6.0.0
@middy/http-header-normalizer (source)	5.5.1 -> 6.0.0
@middy/http-json-body-parser (source)	5.5.1 -> 6.0.0
@middy/http-response-serializer (source)	5.5.1 -> 6.0.0
@middy/validator (source)	5.5.1 -> 6.0.0

---

Release Notes

middyjs/middy (@​middy/core)

v6.0.0

Compare Source

For full details and upgrade guide see https://middy.js.org/docs/upgrade/5-6

Notable changes

• Deprecate Node.js v18.x.
• Add support for Node.js v22.x.
• Add support for --experimental-require-module

What's Changed

• feat(http-security-headers): support report only mode by @​naorpeled in https://github.com/middyjs/middy/pull/1254

Thanks to @​ehmicky for contributing to this release.

Full Changelog: middyjs/middy@5.5.1...6.0.0

---

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 these updates 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: lambda/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @aws-lambda-powertools/[email protected]
npm error Found: @middy/[email protected]
npm error node_modules/@middy/core
npm error   @middy/core@"6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @middy/core@"4.x || 5.x" from @aws-lambda-powertools/[email protected]
npm error node_modules/@aws-lambda-powertools/logger
npm error   @aws-lambda-powertools/logger@"2.11.0" from the root project
npm error
npm error Conflicting peer dependency: @middy/[email protected]
npm error node_modules/@middy/core
npm error   peerOptional @middy/core@"4.x || 5.x" from @aws-lambda-powertools/[email protected]
npm error   node_modules/@aws-lambda-powertools/logger
npm error     @aws-lambda-powertools/logger@"2.11.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-12-07T01_01_35_583Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-07T01_01_35_583Z-debug-0.log