Skip to content

chore(deps): update dependency undici to v8.8.0#577

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/undici-8.x-lockfile
Open

chore(deps): update dependency undici to v8.8.0#577
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/undici-8.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
undici (source) 8.7.08.8.0 age confidence

Release Notes

nodejs/undici (undici)

v8.8.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 added the dependencies Pull requests that update a dependency file label Jul 20, 2026
@renovate
renovate Bot force-pushed the renovate/undici-8.x-lockfile branch from 3e71cfd to b81be51 Compare July 20, 2026 22:13
@renovate
renovate Bot force-pushed the renovate/undici-8.x-lockfile branch from b81be51 to 0a8f784 Compare July 21, 2026 12:49
@renovate
renovate Bot force-pushed the renovate/undici-8.x-lockfile branch from 0a8f784 to c9020bf Compare July 22, 2026 05:56
@renovate

renovate Bot commented Jul 22, 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
? Verifying lockfile against supply-chain policies (1164 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
.                                        | [WARN] deprecated conventional-changelog-cli@5.0.0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 38, reused 0, downloaded 1, added 0
Progress: resolved 39, reused 0, downloaded 1, added 0
Progress: resolved 191, reused 0, downloaded 1, added 0
Progress: resolved 302, reused 0, downloaded 1, added 0
Progress: resolved 415, reused 0, downloaded 1, added 0
Progress: resolved 473, reused 0, downloaded 1, added 0
Progress: resolved 711, reused 0, downloaded 1, added 0
Progress: resolved 966, reused 0, downloaded 1, added 0
Progress: resolved 1126, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (1164 entries in 12.2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @vue/language-plugin-pug@3.3.8 was published at 2026-07-22T15:54:26.210Z, within the minimumReleaseAge cutoff (2026-07-21T22:03:05.964Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants