chore(deps): update dependency reflect-metadata to v0.2.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
reflect-metadata (source)	^0.1.13 → ^0.1.13 || ^0.2.0
reflect-metadata (source)	0.1.14 → 0.2.2

---

Release Notes

rbuckton/reflect-metadata (reflect-metadata)

v0.2.2

Compare Source

v0.2.1

Compare Source

What's Changed

• Fix stack overflow crash in isProviderFor by @​rbuckton in #​155
• Update main to v0.2.1 by @​rbuckton in #​156

Full Changelog: microsoft/reflect-metadata@v0.2.0...v0.2.1

v0.2.0: reflect-metadata 0.2.0

Compare Source

What's Changed

• Add /lite and /no-conflict exports by @​rbuckton in #​144
• No dynamic evaluation in /lite mode by @​rbuckton in #​149

Full Changelog: microsoft/reflect-metadata@v0.1.14...v0.2.0

---

Configuration

📅 Schedule: (UTC)

• 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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/common@8.4.7
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.7
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"8.4.7" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.7
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"8.4.7" from the root project
npm ERR!     1 more (@nestjs/platform-express)
npm ERR!   1 more (@nestjs/platform-express)
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.7
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"8.4.7" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.7
npm ERR!     node_modules/@nestjs/core
npm ERR!       dev @nestjs/core@"8.4.7" from the root project
npm ERR!       1 more (@nestjs/platform-express)
npm ERR!     1 more (@nestjs/platform-express)
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/2024-04-26T09_02_29_076Z-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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/common@8.4.7
npm ERR! Found: reflect-metadata@0.2.2
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.7
npm ERR! node_modules/@nestjs/common
npm ERR!   dev @nestjs/common@"8.4.7" from the root project
npm ERR!   peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.7
npm ERR!   node_modules/@nestjs/core
npm ERR!     dev @nestjs/core@"8.4.7" from the root project
npm ERR!     1 more (@nestjs/platform-express)
npm ERR!   1 more (@nestjs/platform-express)
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/common@8.4.7
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"8.4.7" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0" from @nestjs/core@8.4.7
npm ERR!     node_modules/@nestjs/core
npm ERR!       dev @nestjs/core@"8.4.7" from the root project
npm ERR!       1 more (@nestjs/platform-express)
npm ERR!     1 more (@nestjs/platform-express)
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 /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-08-26T16_50_56_795Z-debug-0.log