Skip to content

chore(deps): bump @types/node to ^26 (synced lockfile)#8

Merged
CodeWithJuber merged 1 commit into
masterfrom
fix/types-node-26
Jul 5, 2026
Merged

chore(deps): bump @types/node to ^26 (synced lockfile)#8
CodeWithJuber merged 1 commit into
masterfrom
fix/types-node-26

Conversation

@CodeWithJuber

Copy link
Copy Markdown
Owner

Supersedes #4. Dependabot's #4 branch had a drifted lockfile (package.json typescript@5.9.3 vs lock 6.0.3) after the TypeScript-6 PR merged ahead of it, so npm ci failed with EUSAGE before any test ran.

This reconstructs the bump on top of current master with a regenerated, in-sync lockfile.

Verified locally on @types/node 26.1.0: typecheck clean, 140/140 tests pass, npm ci exit 0.

Regenerate lockfile on top of current master (typescript@6) so package.json
and package-lock.json are in sync — fixes the npm ci EUSAGE failure on PR #4.
Typecheck clean, 140 tests pass on @types/node 26.1.0.
@CodeWithJuber
CodeWithJuber merged commit 15cceca into master Jul 5, 2026
7 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1992702f35

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package-lock.json
"version": "22.20.0",
"resolved": "https://registry.npmjs.org/@types/node/-/node-22.20.0.tgz",
"integrity": "sha512-QWlFW2wf3nTjC13/DqRnBpR4ZO36VJH/JVBkA/vcnmbTBNQIlnObqyqZE1tUR7+Ni23Lda8R1BxMfbXRpCUx5g==",
"version": "26.1.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Respect the release-age gate before pinning fresh types

When this repo is installed with npm 11.10+ or a registry policy that honors the checked-in .npmrc min-release-age=7, this pinned @types/node@26.1.0 is still inside the seven-day cooldown for the July 5, 2026 commit; npm's v11 config docs say min-release-age only installs versions available more than the configured days ago and errors if none are available. That makes npm ci fail in those environments until the package ages out or the dependency is explicitly excluded, despite the commit message claiming the lockfile is immediately installable.

Useful? React with 👍 / 👎.

@CodeWithJuber CodeWithJuber self-assigned this Jul 5, 2026
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