Skip to content

chore(deps): lock file maintenance#2120

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance
Open

chore(deps): lock file maintenance#2120
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (in timezone Etc/UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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


Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

Code Coverage

@renovate renovate Bot requested a review from a team as a code owner June 1, 2026 03:49
@renovate renovate Bot added the dep-bump label Jun 1, 2026
@renovate

renovate Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: uv.lock
Command failed: uv lock --upgrade
Using CPython 3.14.6 interpreter at: /opt/containerbase/tools/python/3.14.6/bin/python3
  × No solution found when resolving dependencies:
  ╰─▶ Because mkdocs-code-siemens-code-docs-theme was not
      found in the package registry and element depends on
      mkdocs-code-siemens-code-docs-theme>=8.1,<9, we can conclude that
      element's requirements are unsatisfiable.
      And because your workspace requires element, we can conclude that your
      workspace's requirements are unsatisfiable.

hint: An index URL (https://code.siemens.com/api/v4/groups/3259/-/packages/pypi/simple) could not be queried due to a lack of valid authentication credentials (401 Unauthorized)
File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: siemens-element@49.12.0
npm error Found: @vitest/browser-playwright@4.1.9
npm error node_modules/@vitest/browser-playwright
npm error   dev @vitest/browser-playwright@"4.1.8" from the root project
npm error   peerOptional @vitest/browser-playwright@"4.1.9" from vitest@4.1.9
npm error   node_modules/vitest
npm error     dev vitest@"4.1.8" from the root project
npm error     peerOptional vitest@"^4.0.8" from @angular/build@21.1.1
npm error     node_modules/@angular/build
npm error       dev @angular/build@"21.1.1" from the root project
npm error       1 more (@angular-builders/custom-esbuild)
npm error     6 more (@angular-builders/custom-esbuild, @angular/build, ...)
npm error
npm error Could not resolve dependency:
npm error dev @vitest/browser-playwright@"4.1.8" from the root project
npm error
npm error Conflicting peer dependency: vitest@4.1.8
npm error node_modules/vitest
npm error   peer vitest@"4.1.8" from @vitest/browser-playwright@4.1.8
npm error   node_modules/@vitest/browser-playwright
npm error     dev @vitest/browser-playwright@"4.1.8" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-06-24T08_43_04_463Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-24T08_43_04_463Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from bf827b0 to ed30fb9 Compare June 2, 2026 07:15
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from ed30fb9 to 875fdf8 Compare June 9, 2026 18:12
@spike-rabbit spike-rabbit force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from ef72001 to 08f6279 Compare June 10, 2026 14:44
@timowolf timowolf added this pull request to the merge queue Jun 11, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Jun 11, 2026
@spike-rabbit spike-rabbit added this pull request to the merge queue Jun 11, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Jun 11, 2026
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 08f6279 to a4cceca Compare June 11, 2026 09:35
@spike-rabbit spike-rabbit force-pushed the renovate/lock-file-maintenance branch from a4cceca to 8e285ce Compare June 11, 2026 10:59
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 7953e0f to 582164f Compare June 17, 2026 09:27
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 582164f to 3e982af Compare June 19, 2026 12:43
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 3e982af to 99bfd88 Compare June 24, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants