Skip to content

⬆️ Update dependency @types/node to v24#261

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

⬆️ Update dependency @types/node to v24#261
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-24.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Oct 28, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^20.5.7^24.0.0 age confidence

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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.

🔕 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.

@bolt-new-by-stackblitz
Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate Bot force-pushed the renovate/node-24.x branch 3 times, most recently from 65ab11a to 1d72e58 Compare November 3, 2025 03:57
@renovate renovate Bot force-pushed the renovate/node-24.x branch 2 times, most recently from c943500 to a4ade65 Compare November 12, 2025 16:59
@renovate renovate Bot force-pushed the renovate/node-24.x branch 3 times, most recently from 603c2c1 to 9379ca1 Compare December 9, 2025 07:36
@renovate renovate Bot force-pushed the renovate/node-24.x branch 3 times, most recently from 326515a to 514d5ba Compare December 14, 2025 06:52
@renovate renovate Bot force-pushed the renovate/node-24.x branch from 514d5ba to 7da515d Compare December 31, 2025 18:32
@renovate renovate Bot force-pushed the renovate/node-24.x branch 7 times, most recently from e5f0ce7 to 4b1008c Compare January 15, 2026 22:44
@renovate renovate Bot force-pushed the renovate/node-24.x branch from 4b1008c to 48aaa6c Compare January 23, 2026 21:03
@renovate renovate Bot force-pushed the renovate/node-24.x branch 7 times, most recently from 06a07bb to 45ea258 Compare February 8, 2026 06:06
@renovate renovate Bot force-pushed the renovate/node-24.x branch from 45ea258 to c0c106d Compare February 10, 2026 15:40
@renovate renovate Bot force-pushed the renovate/node-24.x branch from c0c106d to d72abce Compare February 26, 2026 04:15
@renovate renovate Bot force-pushed the renovate/node-24.x branch 4 times, most recently from 2f67240 to ab239ea Compare February 28, 2026 06:34
@renovate renovate Bot force-pushed the renovate/node-24.x branch 2 times, most recently from 0dda239 to 305d187 Compare March 6, 2026 06:56
@renovate renovate Bot force-pushed the renovate/node-24.x branch from 305d187 to 2fbfd23 Compare March 13, 2026 19:35
@renovate renovate Bot force-pushed the renovate/node-24.x branch 4 times, most recently from d04ebfb to 449ff84 Compare April 7, 2026 22:44
@renovate renovate Bot force-pushed the renovate/node-24.x branch from 449ff84 to e4c284f Compare April 29, 2026 17:31
@renovate renovate Bot force-pushed the renovate/node-24.x branch 4 times, most recently from b841242 to bcb5816 Compare May 12, 2026 02:51
@renovate renovate Bot force-pushed the renovate/node-24.x branch from bcb5816 to 7a988f2 Compare May 18, 2026 13:26
@renovate renovate Bot force-pushed the renovate/node-24.x branch from 7a988f2 to d74d33d Compare June 5, 2026 23:56
@renovate renovate Bot force-pushed the renovate/node-24.x branch from d74d33d to 773ff26 Compare June 6, 2026 03:09
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jun 6, 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 (506 entries)...
✗ Lockfile failed supply-chain policy check (506 entries in 2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @types/node@20.19.42 was published at 2026-06-05T22:33:41.468Z, within the minimumReleaseAge cutoff (2026-06-05T03:08:54.930Z)

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