Skip to content

📦 update to v#44

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

📦 update to v#44
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/lock-file-maintenance

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 8, 2025

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: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate Bot requested a review from eonova as a code owner December 8, 2025 01:44
@vercel
Copy link
Copy Markdown

vercel Bot commented Dec 8, 2025

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

Project Deployment Actions Updated (UTC)
eonova Ready Ready Preview, Comment, Open in v0 Mar 13, 2026 3:47pm

@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 71190d7 to 3f8a204 Compare December 8, 2025 18:14
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 3f8a204 to 32ff30f Compare December 31, 2025 16:01
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 32ff30f to 5393431 Compare January 5, 2026 13:33
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5393431 to 70b01a9 Compare January 8, 2026 17:49
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 70b01a9 to 7d39bfa Compare January 19, 2026 16:10
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 7d39bfa to 348974d Compare January 23, 2026 18:29
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 348974d to 480a577 Compare February 6, 2026 09:31
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 480a577 to e93d8a5 Compare February 12, 2026 16:42
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from e93d8a5 to bf4a318 Compare February 17, 2026 18:47
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from bf4a318 to 18730d0 Compare March 5, 2026 14:10
@renovate renovate Bot force-pushed the renovate/lock-file-maintenance branch from 18730d0 to 8c61b4d Compare March 13, 2026 15:43
@sonarqubecloud
Copy link
Copy Markdown

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 14, 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
.                                        |  WARN  deprecated @antfu/nip@0.1.1
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        |  WARN  deprecated @react-email/preview-server@4.3.2
Progress: resolved 34, reused 0, downloaded 0, added 0
Progress: resolved 48, reused 0, downloaded 0, added 0
.                                        |  WARN  deprecated @react-email/components@0.5.7
Progress: resolved 60, reused 0, downloaded 0, added 0
Progress: resolved 79, reused 0, downloaded 0, added 0
Progress: resolved 96, reused 0, downloaded 0, added 0
Progress: resolved 112, reused 0, downloaded 0, added 0
Progress: resolved 135, reused 0, downloaded 0, added 0
Progress: resolved 139, reused 0, downloaded 0, added 0
 WARN  Request took 10260ms: https://registry.npmjs.org/next
Progress: resolved 140, reused 0, downloaded 0, added 0
 WARN  Request took 11169ms: https://registry.npmjs.org/drizzle-orm
Progress: resolved 141, reused 0, downloaded 0, added 0
Progress: resolved 166, reused 0, downloaded 0, added 0
Progress: resolved 188, reused 0, downloaded 0, added 0
Progress: resolved 193, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "chokidar@4.0.3" (possible package takeover)

This error happened while installing the dependencies of @content-collections/core@0.14.3

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants