Bump @types/node from 26.2.0 to 26.4.0

[dependabot]

Bumps @types/node from 26.2.0 to 26.4.0.

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 — append one bullet to ChangeLog.md under ## Upcoming Release → General:, matching the existing style and tone of the entries already there (package name in backticks, old → new version, why, and a one-line concise summary of any code changes made).
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...

Addressed in d711baf.

Impact analysis

• Package: @types/node (direct dev dependency; explicitly loaded by tsconfig.json)
• Old version: 26.2.0
• New version: 26.4.0
• Change Impact: Lockfile-only type declaration update affecting compile-time checks for broadly used Node APIs (Buffer, streams, filesystem, HTTP, process); no runtime code change.

Build/Conflict Issues

• Commands: npm ci --legacy-peer-deps; npm run build; npm run lint
• Result: All passed; no merge conflicts or tracked install changes.

Tests

• Added: None.
• Updated: tests/blob/fsStore.test.ts now verifies a non-zero-offset sliced Buffer is persisted as the intended view only.
• Result: Focused test passed (4/4).

Run the Suite

• Commands: npm run test:blob
• Status: Passed: 568 passing, 3 pending.

Changelog

• Entry: Recorded the 26.2.0 → 26.4.0 lockfile update, rationale, no application changes, and sliced-Buffer coverage.
• Location: ChangeLog.md, ## Upcoming Release → General:.

Comments

• Reviewed: All PR comments, reviews, and review threads, including resolved/hidden threads; CI runs and available logs also reviewed.
• Actions: No other actionable or unresolved feedback. Post-push action_required runs contain zero jobs and are approval-gated rather than failures.

Self-Rate

• Score: 10/10
• Reasoning: Dependency impact, meaningful coverage, changelog, install/build/lint, Blob suite, secret scan, CodeQL assessment, CI, and comments were all addressed; worktree is clean.

Summary

• Why this matters: Keeps Azurite’s compile-time Node API model current and verifies Buffer-view behavior used by filesystem persistence.
• Risk of not taking change: Azurite would retain older Node declarations and miss newer typing corrections, increasing future compiler/API drift.

[Copilot]

🟢 Approval recommended

The changes are low-risk (lockfile-only type update plus a targeted test improvement) and the new test specifically guards against offset/length handling regressions for Buffer views.

Review details

• Files reviewed: 2/3 changed files
• Comments generated: 0 new
• Review effort level: Lite