Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 28, 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: 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.

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 296fa95 to 8077510 Compare June 18, 2025 10:03
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 5 times, most recently from 0479ce1 to ea38303 Compare July 6, 2025 06:01
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from b7d1f9f to 2b99b82 Compare July 9, 2025 14:33
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from af494b5 to afca38c Compare August 13, 2025 12:29
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 4 times, most recently from 39779f7 to 97f6786 Compare August 25, 2025 10:13
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 97f6786 to 94cf059 Compare August 31, 2025 12:10
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 94cf059 to 146a540 Compare September 17, 2025 02:05
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 146a540 to 97bf6d6 Compare September 25, 2025 17:15
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from b425100 to 5f28613 Compare October 5, 2025 18:33
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from da63c52 to ccd8765 Compare October 21, 2025 19:04
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from ccd8765 to 0e928be Compare November 10, 2025 21:46
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 0e928be to 7baf0e9 Compare November 18, 2025 23:27
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 7247031 to 9344f60 Compare December 1, 2025 17:43
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from 1172e6c to dac3e59 Compare December 4, 2025 21:39
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from dac3e59 to a18e6e8 Compare December 11, 2025 22:39
@renovate
Copy link
Contributor Author

renovate bot commented Dec 11, 2025

⚠️ 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 2 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 31, reused 0, downloaded 0, added 0
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 132, reused 0, downloaded 0, added 0
 ERR_PNPM_TRUST_DOWNGRADE  High-risk trust downgrade for "eslint-import-resolver-typescript@3.10.1" (possible package takeover)

This error happened while installing the dependencies of @nuxtjs/eslint-config-typescript@12.1.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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant