Skip to content

Conversation

taiga-family-bot
Copy link
Member

This PR contains the following updates:

Package Type Change
@ng-web-apis/common (source) devDependencies 4.12.0 -> 4.12.2
@ng-web-apis/universal (source) devDependencies 4.12.0 -> 4.12.2

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@taiga-family-bot
Copy link
Member Author

taiga-family-bot commented Oct 6, 2025

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn Unknown user config "always-auth". 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: ng-polymorpheus@4.9.0
npm error Found: @types/node@22.18.8
npm error node_modules/@types/node
npm error   dev @types/node@"22.18.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @types/node@">=24.6.2" from @ng-web-apis/universal@4.12.2
npm error node_modules/@ng-web-apis/universal
npm error   dev @ng-web-apis/universal@"4.12.2" 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 /home/runner/.npm/_logs/2025-10-15T04_31_28_988Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-10-15T04_31_28_988Z-debug-0.log

File name: undefined
Command failed: ws=$(node -p '!!require(`./package.json`).workspaces') && npm i -ws=$ws --include-workspace-root=$ws && npm i -ws=$ws --include-workspace-root=$ws
npm warn Unknown user config "always-auth". 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: ng-polymorpheus@4.9.0
npm error Found: @types/node@22.18.8
npm error node_modules/@types/node
npm error   dev @types/node@"22.18.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @types/node@">=24.6.2" from @ng-web-apis/universal@4.12.2
npm error node_modules/@ng-web-apis/universal
npm error   dev @ng-web-apis/universal@"4.12.2" 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 /home/runner/.npm/_logs/2025-10-15T04_31_30_660Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-10-15T04_31_30_660Z-debug-0.log

@taiga-family-bot taiga-family-bot requested a review from a team as a code owner October 6, 2025 12:56
@taiga-family-bot taiga-family-bot requested review from MarsiBarsi, mdlufy, nsbarsukov, vladimirpotekhin and waterplea and removed request for a team October 6, 2025 12:56
@taiga-family-bot taiga-family-bot force-pushed the renovate/@ng-web-apis-deps branch from fa1a016 to 29a6156 Compare October 7, 2025 09:33
@taiga-family-bot taiga-family-bot force-pushed the renovate/@ng-web-apis-deps branch from 29a6156 to 35601a2 Compare October 8, 2025 12:53
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