[NEUTRAL] Update dependency reflect-metadata to v0.2.2 - autoclosed

[mend-for-github-com]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
reflect-metadata (source)	0.1.13 -> 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 https://github.com/rbuckton/reflect-metadata/pull/155
• Update main to v0.2.1 by @​rbuckton in https://github.com/rbuckton/reflect-metadata/pull/156

Full Changelog: rbuckton/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 https://github.com/rbuckton/reflect-metadata/pull/144
• No dynamic evaluation in /lite mode by @​rbuckton in https://github.com/rbuckton/reflect-metadata/pull/149

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

v0.1.14: reflect-metadata 0.1.14

Compare Source

What's Changed

• Fix variable name by @​amatiasq in https://github.com/rbuckton/reflect-metadata/pull/109
• Bypass webpack process.env inlining by @​rbuckton in c8c06cc

New Contributors

• @​amatiasq made their first contribution in https://github.com/rbuckton/reflect-metadata/pull/109

Full Changelog: rbuckton/reflect-metadata@v0.1.13...v0.1.14

---

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, check this box

[mend-for-github-com]

⚠ 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: yarn.lock

Internal Error: Error when performing the request to https://registry.npmjs.org/yarn; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:22878:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:22892:20)
    at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:22942:20)
    at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:22975:14)
    at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:23537:25)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:23644:30)
    at async BinaryCommand.validateAndExecute (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:21164:22)
    at async _Cli.run (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:22139:18)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.26.0/node_modules/corepack/dist/lib/corepack.cjs:24371:12)