build: lock file maintenance
This PR contains the following updates:
| Update | Change |
|---|---|
| lockFileMaintenance | All locks refreshed |
[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: Branch creation - "before 4am on monday" in timezone America/Tijuana, 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 has been generated by Renovate Bot.
⚠️ 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: bazel/pnpm-lock.yaml
integration/tests/package_mappings | WARN The field "resolutions" was found in /tmp/renovate/repos/github/angular/dev-infra/bazel/integration/tests/package_mappings/package.json. This will not take effect. You should configure "resolutions" at the root of the workspace instead.
Scope: all 15 projects
Progress: resolved 1, reused 0, downloaded 0, added 0
undefined
/tmp/renovate/repos/github/angular/dev-infra/bazel/integration/tests/package_mappings:
ERR_PNPM_INVALID_SELECTOR Cannot parse the "**/fake_pkg" selector
This PR was merged into the repository by commit f9c5a8162b545410f7b08567591a9d242488bcb6.
The changes were merged into the following branches: main
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.