Repository navigation
chore(deps-dev): bump @types/node from 26.6.1 to 26.6.5 - #382
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 26.6.1 to 26.6.5. - [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.6.5 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Automated maintainer triage (PeterGuy326 duty rotation). Blocked — no action needed from the author. Blocker: All other required checks are green ( This is a |
Updates the resolved
@types/nodeversion from 26.6.1 to 26.6.5 inpackage.jsonand the generated lockfile; this is a development-dependency type update. No application source changes are included.Canonical requirement
Delivery ownership
Requirement trace
@types/nodeversion 26.6.1 to 26.6.5 update inpackage.jsonandpackage-lock.jsonFile domains
@types/nodeversion 26.6.1 to 26.6.5 update inpackage.jsonandpackage-lock.json; no application runtime source is changed.Scope and non-goals
This PR updates only the the resolved
@types/nodeversion development dependency resolution inpackage.jsonandpackage-lock.json. It does not change product behavior, APIs, data formats, or release policy beyond the stated dependency/action update.Validation
npm test; governance commandnpm run governance:check -- --github-event-file "$GITHUB_EVENT_PATH".Security and compatibility
The change is a within-range patch update of a development-only type package and leaves runtime packages, workflow permissions, publication policy, and application code unchanged. Hosted dependency review and the supported Node-version matrix remain required.
Known limitations
The governance-only failed jobs must be rerun after restoring this body. No local result substitutes for required hosted checks.
Risk and rollback
Risk is limited to TypeScript type-check compatibility. Rollback is the two-file manifest/lockfile revert; there is no data migration or irreversible side effect.
Product review handoff