Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 5, 2025

This PR contains the following updates:

Package Change Age Confidence
@doist/ui-extensions-server 3.4.1 -> 3.5.6 age confidence

Release Notes

Doist/ui-extensions-server (@​doist/ui-extensions-server)

v3.5.6

Compare Source

v3.5.5

Compare Source

v3.5.4

Compare Source

v3.5.3

Compare Source

v3.5.2

Compare Source

v3.5.1

Compare Source

v3.5.0

Compare Source


Configuration

📅 Schedule: Branch creation - Monday through Friday ( * * * * 1-5 ) (UTC), 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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Nov 5, 2025

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"0.1.13" from the root project
npm error   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"10.4.20" from the root project
npm error     peer @nestjs/common@"^8.4.7 || ^9.0.0 || ^10.0.0" from @doist/[email protected]
npm error     node_modules/@doist/ui-extensions-server
npm error       @doist/ui-extensions-server@"3.5.6" from the root project
npm error     8 more (@nestjs/axios, @nestjs/config, @nestjs/core, ...)
npm error   4 more (@nestjs/core, @nestjs/microservices, ...)
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.14 || ^0.2.0" from [email protected]
npm error node_modules/typeorm
npm error   typeorm@"0.3.27" from the root project
npm error   peer typeorm@"^0.3.7" from @doist/[email protected]
npm error   node_modules/@doist/ui-extensions-server
npm error     @doist/ui-extensions-server@"3.5.6" from the root project
npm error   1 more (@nestjs/typeorm)
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 /runner/cache/others/npm/_logs/2025-11-18T23_41_04_641Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-18T23_41_04_641Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant