Skip to content

Update dependency @types/node to v25.9.1#30

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-25.x-lockfile
Open

Update dependency @types/node to v25.9.1#30
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-25.x-lockfile

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 12, 2026

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 25.6.225.9.1 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • Between 08:00 AM and 02:59 PM, Monday through Friday (* 8-14 * * 1-5)

🚦 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 force-pushed the renovate/node-25.x-lockfile branch from e006684 to fca419f Compare May 12, 2026 16:04
@renovate renovate Bot enabled auto-merge May 14, 2026 19:45
@renovate renovate Bot force-pushed the renovate/node-25.x-lockfile branch from fca419f to 902ec52 Compare May 14, 2026 19:45
@renovate renovate Bot changed the title Update dependency @types/node to v25.7.0 Update dependency @types/node to v25.8.0 May 14, 2026
@renovate renovate Bot force-pushed the renovate/node-25.x-lockfile branch 2 times, most recently from 2cfb8e8 to fda54c6 Compare May 18, 2026 12:51
@renovate renovate Bot changed the title Update dependency @types/node to v25.8.0 Update dependency @types/node to v25.9.0 May 18, 2026
@renovate renovate Bot changed the title Update dependency @types/node to v25.9.0 Update dependency @types/node to v25.9.1 May 19, 2026
@renovate renovate Bot force-pushed the renovate/node-25.x-lockfile branch 4 times, most recently from c080b0f to 5be535e Compare May 27, 2026 10:31
@renovate renovate Bot force-pushed the renovate/node-25.x-lockfile branch 3 times, most recently from 29aad05 to 3205a1b Compare May 30, 2026 23:42
@renovate renovate Bot force-pushed the renovate/node-25.x-lockfile branch from 3205a1b to f82fea5 Compare June 2, 2026 00:49
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jun 2, 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
? Verifying lockfile against supply-chain policies (469 entries)...
✗ Lockfile failed supply-chain policy check (469 entries in 2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 20 lockfile entries failed verification:
  @oxlint/binding-android-arm-eabi@1.68.0 was published at 2026-06-01T17:06:31.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-android-arm64@1.68.0 was published at 2026-06-01T17:06:00.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-darwin-arm64@1.68.0 was published at 2026-06-01T17:05:55.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-darwin-x64@1.68.0 was published at 2026-06-01T17:07:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-freebsd-x64@1.68.0 was published at 2026-06-01T17:07:30.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-arm-gnueabihf@1.68.0 was published at 2026-06-01T17:06:37.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-arm-musleabihf@1.68.0 was published at 2026-06-01T17:06:43.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-arm64-gnu@1.68.0 was published at 2026-06-01T17:06:13.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-arm64-musl@1.68.0 was published at 2026-06-01T17:06:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-ppc64-gnu@1.68.0 was published at 2026-06-01T17:06:55.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-riscv64-gnu@1.68.0 was published at 2026-06-01T17:07:01.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-riscv64-musl@1.68.0 was published at 2026-06-01T17:07:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-s390x-gnu@1.68.0 was published at 2026-06-01T17:07:13.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-x64-gnu@1.68.0 was published at 2026-06-01T17:07:38.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-linux-x64-musl@1.68.0 was published at 2026-06-01T17:07:45.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-openharmony-arm64@1.68.0 was published at 2026-06-01T17:06:25.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-win32-arm64-msvc@1.68.0 was published at 2026-06-01T17:06:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-win32-ia32-msvc@1.68.0 was published at 2026-06-01T17:06:48.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  @oxlint/binding-win32-x64-msvc@1.68.0 was published at 2026-06-01T17:07:25.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)
  oxlint@1.68.0 was published at 2026-06-01T17:07:52.000Z, within the minimumReleaseAge cutoff (2026-06-01T13:40:15.724Z)

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants