Skip to content

chore(deps): lock file maintenance#679

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 23, 2026

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 - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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.

👻 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.

@vercel
Copy link

vercel bot commented Feb 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
magic-regexp-docs Ready Ready Preview, Comment Feb 23, 2026 2:54am

@github-actions
Copy link

Diagnostics Comparison:

Click to expand
Metric Previous New Status
Files 355 355 ± (0.00%)
Lines 159892 159892 ± (0.00%)
Identifiers 152369 152369 ± (0.00%)
Symbols 252910 252910 ± (0.00%)
Types 49252 49252 ± (0.00%)
Instantiations 390222 390222 ± (0.00%)
Memory used 348796K 304034K ▼ (-14.72%)
I/O read 0.02s 0.03s ▲ (+33.33%)
I/O write 0s 0s ± (0.00%)
Parse time 0.66s 0.7s ± (+5.71%)
Bind time 0.28s 0.27s ± (-3.70%)
Check time 1.57s 1.53s ± (-2.61%)
Emit time 0.08s 0.07s ± (-14.29%)
Total time 2.58s 2.58s ± (0.00%)

@codspeed-hq
Copy link

codspeed-hq bot commented Feb 23, 2026

Merging this PR will not alter performance

✅ 6 untouched benchmarks


Comparing renovate/lock-file-maintenance (ecc335b) with main (1f8e8b2)

Open in CodSpeed

@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 2026

⚠️ 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: pnpm-lock.yaml
Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 0, added 0
Progress: resolved 102, reused 0, downloaded 0, added 0
Progress: resolved 181, reused 0, downloaded 0, added 0
Progress: resolved 242, reused 0, downloaded 0, added 0
Progress: resolved 397, reused 0, downloaded 0, added 0
Progress: resolved 533, reused 0, downloaded 0, added 0
Progress: resolved 647, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/unjs/magic-regexp/docs:
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "semver@6.3.1" (possible package takeover)

This error happened while installing the dependencies of nuxt@4.3.1
 at @nuxt/vite-builder@4.3.1
 at @vitejs/plugin-vue-jsx@5.1.5
 at @babel/core@7.29.0

Trust checks are based solely on publish date, not semver. A package cannot be installed if any earlier-published version had stronger trust evidence. Earlier versions had provenance attestation, but this version has no trust evidence. A trust downgrade may indicate a supply chain incident.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants