Skip to content

🔨 Lock file maintenance - #2715

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

🔨 Lock file maintenance#2715
w5s-automator[bot] wants to merge 1 commit into
mainfrom
w5s-automator/lock-file-maintenance

Conversation

@w5s-automator

@w5s-automator w5s-automator Bot commented Aug 24, 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 Europe/Paris)

  • Branch creation
    • "before 6am on Monday"
  • 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 has been generated by Mend Renovate CLI.

@w5s-automator
w5s-automator Bot enabled auto-merge (squash) August 24, 2026 01:20
@w5s-automator
w5s-automator Bot force-pushed the w5s-automator/lock-file-maintenance branch 7 times, most recently from de9e0bf to ebcf54a Compare September 3, 2026 22:41
@w5s-automator
w5s-automator Bot force-pushed the w5s-automator/lock-file-maintenance branch from ebcf54a to b1fe3b0 Compare September 3, 2026 23:09
@w5s-automator

w5s-automator Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 27 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 0, added 0
Progress: resolved 279, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/w5s/std/apps/website:
[ERR_PNPM_TRUST_DOWNGRADE] High-risk trust downgrade for "webpack-dev-middleware@7.4.6" (possible package takeover)

This error happened while installing the dependencies of @docusaurus/core@3.10.2
 at webpack-dev-server@5.2.6

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 trusted publisher, 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