Bump fs-extra from 11.4.0 to 11.4.1

[dependabot]

Bumps fs-extra from 11.4.0 to 11.4.1.

Changelog

Sourced from fs-extra's changelog.

11.4.1 / 2026-09-22

• Properly handle read errors (e.g. due to permissions) in emptyDir*() (#1080)
• Allow renaming with only Unicode normalization difference in the filename (APFS-specific) (#859, #1079)

Commits

• 1e223d3 11.4.1
• 8cfd0a0 Remove obsolete docs note
• de72292 Treat Unicode-normalization-only renames like case-only renames (#1079)
• 7e0ce7f Remove broken link (#1083)
• 00e858c Update GH Actions versions (#1082)
• f829cc9 fix: propagate emptyDir directory read errors (#1080)
• 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. Check if the Files changed in this pull request are included in default exclusions.

---

💡 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...

Impact analysis

• Package: fs-extra
• Old version: 11.4.0
• New version: 11.4.1
• Change Impact: Patch release with two bugfixes upstream: (1) emptyDir* now properly propagates read errors (e.g. permission errors) instead of swallowing them, (2) renaming files that differ only by Unicode normalization now works on APFS. Azurite only imports access and ensureDir from fs-extra (src/azurite.ts, src/blob/BlobEnvironment.ts, src/common/VSCServerManagerQueue.ts, src/common/VSCEnvironment.ts, src/queue/main.ts, src/table/main.ts) — it never calls emptyDir* or relies on the rename behavior, so the fix has no functional impact on Azurite. No breaking API changes.

Build/Conflict Issues

• Commands: npm ci --legacy-peer-deps, npm run build, npm run lint
• Result: No conflicts. Build and lint both succeed cleanly; npm ls fs-extra confirms 11.4.1 is installed.

Tests

• Added: None — per repo convention, tests should not be added purely to exercise third-party dependency internals for a patch bump that touches unused APIs.
• Updated: None
• Result: N/A

Run the Suite

• Commands: npx mocha -r ts-node/register tests/packageScripts.test.ts, npx mocha -r ts-node/register tests/blob/startupErrorRecovery.test.ts tests/queue/startupErrorRecovery.test.ts (these are the tests exercising the fs-extra code paths Azurite uses)
• Status: All passing (8/8 and 5/5).

Changelog

• Entry: None added
• Location: N/A — this is an internal dependency maintenance update with no user-visible behavior, compatibility, performance, or security change for Azurite users.

Comments

• Reviewed: The prior automated Copilot review comment ("Copilot wasn't able to review any files...") and this instruction comment.
• Actions: Performed impact analysis, verified build/lint, ran targeted tests confirming no regressions. No code changes were required since package-lock.json already reflects the bump and no source changes are needed.

Self-Rate

• Score: 9
• Reasoning: Impact analysis, build/lint verification, and targeted test runs are complete and passing. No changelog/tests were needed given the change only touches unused fs-extra APIs. Slight deduction only because there's inherent uncertainty in fully verifying an upstream dependency's internal fix without its own test suite.

Summary

• Why this matters: Keeps fs-extra current with upstream bugfixes (error handling, Unicode filename support) with zero functional risk to Azurite.
• Risk of not taking change: Low — the fixed bugs aren't in code paths Azurite uses, but staying on 11.4.1 avoids drifting from security/bugfix patches and keeps the lockfile consistent with dependency scanning.