build(deps): bump @types/node from 24.13.3 to 26.5.0 in the types group across 1 directory - #11984
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps the types group with 1 update in the / directory: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 24.13.3 to 26.5.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.5.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: types ... Signed-off-by: dependabot[bot] <support@github.com>
|
Azure Pipelines: Successfully started running 1 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
🟡 Changes recommended
Regenerate the lockfile so the root importer retains the catalog: specifier.
Get a fresh assessment by requesting another Copilot review.
Pull request overview
Updates @types/node from 24.13.3 to 26.5.0.
Changes:
- Updates the shared Node.js type catalog.
- Refreshes lockfile dependency resolutions.
Critical issue: the lockfile records 26.5.0 instead of retaining the manifest’s catalog: specifier; regenerate it to avoid frozen CI install failures.
File summaries
| File | Summary |
|---|---|
pnpm-workspace.yaml |
Updates the shared @types/node catalog. |
pnpm-lock.yaml |
Refreshes dependency resolutions but has an inconsistent root importer specifier. |
Review details
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
Suppressed comments (2)
pnpm-workspace.yaml:79
- The PR title and description say this updates
@types/nodefrom 24.13.3, but this change is from the repository's^26.3.0catalog (26.4.1 in the lockfile) to 26.5.0. Please refresh the Dependabot metadata or confirm the intended baseline so the review and release notes describe the actual update.
"@types/node": ^26.5.0
pnpm-workspace.yaml:79
- This catalog is used as a published runtime dependency by
packages/spec-coverage-sdk/package.json:31, unlike the many dev-only uses. Changing the catalog therefore changes that package's published dependency metadata; per.chronus/config.yamland the repository changelog instructions, add adependencieschangeset listing@typespec/spec-coverage-sdkbefore merging.
"@types/node": ^26.5.0
- Files reviewed: 1/2 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| "@types/multer": ^2.2.0 | ||
| "@types/mustache": ^4.2.6 | ||
| "@types/node": ^26.3.0 | ||
| "@types/node": ^26.5.0 |
There was a problem hiding this comment.
🔵 Needs a closer look
Generated definitions and the dependency changeset are missing, and the PR metadata needs correction.
Review details
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
Suppressed comments (3)
Previously missed (1) — in code that hasn't changed since the last review.
pnpm-workspace.yaml:79
- The PR description says this updates
@types/nodefrom 24.13.3, but this branch actually changes the workspace range from^26.3.0and the lockfile resolution from 26.4.1 to 26.5.0. Please refresh the PR metadata so it accurately describes the update being reviewed.
pnpm-workspace.yaml:79
- This catalog value is also copied into the checked-in
packages/http-server-js/generated-defs/package.json.tsbybuild-helpers.ts, and the scaffold uses that generatedhsjsDependenciesmap when writing new projects. That file still contains@types/node: ^26.3.0, so scaffolding can emit a stale dependency range after this bump; regenerate/update the generated definition to^26.5.0.
"@types/node": ^26.5.0
pnpm-workspace.yaml:79
- This catalog is a published runtime dependency of
packages/spec-coverage-sdk(package.json:28-33), so changing it changes that package's consumer-facing dependency range. Per.chronus/config.yamland the repository's dependency changesets, add achangeKind: dependenciesentry for@typespec/spec-coverage-sdk; no such entry is included in this PR.
"@types/node": ^26.5.0
- Files reviewed: 1/2 changed files
- Comments generated: 0 new
- Review effort level: Lite
Bumps the types group with 1 update in the / directory: @types/node.
Updates
@types/nodefrom 24.13.3 to 26.5.0Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions