azure-database
azure-database copied to clipboard
Published
20 hours ago •
nestjs
nestjs
fix(deps): update dependency reflect-metadata to v0.2.2
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| reflect-metadata (source) | ^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
v0.2.1
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: https://github.com/rbuckton/reflect-metadata/compare/v0.2.0...v0.2.1
v0.2.0: reflect-metadata 0.2.0
What's Changed
- Add /lite and /no-conflict exports by @rbuckton in https://github.com/rbuckton/reflect-metadata/pull/144
- No dynamic evaluation in
/litemode by @rbuckton in https://github.com/rbuckton/reflect-metadata/pull/149
Full Changelog: https://github.com/rbuckton/reflect-metadata/compare/v0.1.14...v0.2.0
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 these updates again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
⚠ Artifact update problem
Renovate failed to update artifacts 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: sample/table-storage/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! reflect-metadata@"^0.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^10.0.0" from the root project
npm ERR! peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^10.0.0" from the root project
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^10.0.0" from the root project
npm ERR! peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^10.0.0" from the root project
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
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!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_47_679Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_47_679Z-debug-0.log
File name: sample/cosmos-db/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! reflect-metadata@"^0.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^10.0.0" from the root project
npm ERR! peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^10.0.0" from the root project
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^10.0.0" from the root project
npm ERR! peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^10.0.0" from the root project
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
npm ERR! 2 more (@nestjs/platform-express, @nestjs/testing)
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!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_53_864Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-29T04_39_53_864Z-debug-0.log
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
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/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^9.0.0 || ^10.0.0" from the root project
npm ERR! peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^9.0.0 || ^10.0.0" from the root project
npm ERR! 1 more (@nestjs/testing)
npm ERR! 1 more (@nestjs/testing)
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^9.0.0 || ^10.0.0" from the root project
npm ERR! peer @nestjs/common@"^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/core
npm ERR! @nestjs/core@"^9.0.0 || ^10.0.0" from the root project
npm ERR! 1 more (@nestjs/testing)
npm ERR! 1 more (@nestjs/testing)
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-03-29T04_40_18_630Z-debug-0.log