Bump @types/node from 26.6.1 to 26.6.2

[dependabot]

Bumps @types/node from 26.6.1 to 26.6.2.

Commits

• See full diff in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Akanksha Jain (jainakanksha-msft)]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, including the package name and old → new version, then check where that dependency is actually used in the codebase, or whether it is unused, and summarize the potential impact.
2. Fix build/conflict issues — run npm ci --legacy-peer-deps, npm run build, and npm run lint; resolve any merge conflicts, build errors, or lint errors that surface.
3. Tests — add or update tests under tests/** to cover the changed usage, and make sure they meaningfully validate the change (not just re-assert the version bump).
4. Run the suite — run the relevant npm run test:* script(s) for the affected area (e.g. test:blob, test:queue, test:table) and keep fixing until they pass.
5. Changelog — Add a changelog entry only for changes that an Azurite user, operator, SDK developer, or extension user could reasonably observe. Exclude internal maintenance, testing, CI/CD, linting, and development dependency updates unless they result in a user-visible behaviour, compatibility, performance, or security improvement.
6. Comments — review any existing PR comments and review threads, including resolved/hidden ones, and address anything actionable.
7. Self-rate — rate this work 1-10 against: correctness, test coverage, changelog accuracy, build/lint health, and comment resolution.
8. Iterate — if it's not a 10, keep improving until it is before finishing.
9. Summary — your final response must use the following structure exactly (no free-form paragraph summary).

Impact analysis

• Package:
• Old version:
• New version:
• Change Impact:

Build/Conflict Issues

• Commands:
• Result:

Tests

• Added:
• Updated:
• Result:

Run the Suite

• Commands:
• Status:

Changelog

• Entry:
• Location:

Comments

• Reviewed:
• Actions:

Self-Rate

• Score:
• Reasoning:

Summary

• Why this matters:
• Risk of not taking change:

[Copilot]

Copilot This PR was opened by Dependabot. Please take it the rest of the way before it's ready for human review:

1. Impact analysis — review the PR diff/description to identify what changed, i...

Done. Summary below.

Impact analysis

• Package: @types/node
• Old version: 26.6.1 → New version: 26.6.2
• Change Impact: devDependency-only patch bump of TypeScript ambient type definitions (used only at build/type-check time, not shipped in runtime output). package.json already pins ^26.1.2 so only package-lock.json changed. No production code paths reference @types/node directly; risk is negligible.

Build/Conflict Issues

• Commands: npm ci --legacy-peer-deps, npm run build, npm run lint
• Result: No merge conflicts. Install, build, and lint all completed successfully with no errors.

Tests

• Added: None — this is a type-definitions-only bump with no behavioral or API surface change to test.
• Updated: None
• Result: N/A

Run the Suite

• Commands: npx mocha -r ts-node/register tests/packageScripts.test.ts (validates lockfile pinning/tsconfig ambient types, the only suite relevant to this dependency change)
• Status: All 8 tests passed.

Changelog

• Entry: None added
• Location: N/A — devDependency/type-definition bump has no user-visible behavior, compatibility, performance, or security effect for Azurite users, operators, or SDK/extension developers.

Comments

• Reviewed: The bot's "Copilot wasn't able to review any files" comment and this instruction comment.
• Actions: Verified build/lint/tests pass; no code or test changes were required.

Self-Rate

• Score: 10
• Reasoning: Change is verified safe (build, lint, and targeted lockfile tests pass), correctly scoped as no-op for tests/changelog given it's a type-only devDependency patch, and all actionable comments addressed.

Summary

• Why this matters: Keeps TypeScript type definitions current with the latest Node.js types patch release for accurate type-checking during development.
• Risk of not taking change: Minimal — staying on 26.6.1 poses no functional risk, but merging keeps dependencies current and avoids drift from upstream type fixes.