Maintenance updates and API version enhancements and enhanced error handling for the Blob and Queue services

[jainakanksha-msft]

This pull request introduces several dependency updates, service API version bumps, and important fixes for startup and shutdown reliability, as well as refactors to improve error handling and maintainability. The most significant changes are grouped below:

Dependency and API Version Updates:

• Applied npm audit fix and updated dependencies such as axios, morgan, and esbuild to address security vulnerabilities and maintenance issues (package.json). [1] [2]
• Bumped the default Blob, Queue, and Table service API version to 2026-06-06, and added support for 2026-04-06 and 2026-02-06 for these endpoints (ChangeLog.md).

Startup and Shutdown Reliability:

• Fixed issue 3.36.0 Error on Container Start #2672: Improved startup reliability for Blob and Queue services by adding backward-compatible restore for persisted contentMD5 formats and avoiding GC-triggered close() calls during server startup (ChangeLog.md).
• Refactored shutdown logic to include better diagnostics and safer closure of services, ensuring errors during shutdown are logged with context (src/azurite.ts).

Garbage Collection (GC) Critical Error Handling:

• Centralized and improved handling of GC critical errors in Blob and SQL Blob servers by using a new handleGCCriticalErrorClose helper, providing more informative logs and robust shutdown on GC failures (src/blob/BlobServer.ts, src/blob/SqlBlobServer.ts). [1] [2]

Code Quality and Maintainability:

• Refactored and formatted code in LokiBlobMetadataStore for improved readability and maintainability, including better async handling, consistent formatting, and clearer error conditions (src/blob/persistence/LokiBlobMetadataStore.ts). [1] [2] [3] [4]

Documentation:

• Updated ChangeLog.md to clearly document all major changes, fixes, and enhancements for this release. [1] [2]

[Copilot]

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

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

ChangeLog.md:9

• Changelog entry is grammatically awkward (“Applied npm audit fix to updates…”). Consider rephrasing so the sentence reads clearly.

- Applied npm audit fix to updates across multiple dependencies to address security vulnerabilities and maintenance updates.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 7 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 7 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

ChangeLog.md:9

• Wording/grammar: “Applied npm audit fix to updates…” is awkward and reads like a partial sentence. Consider rephrasing to make the changelog entry clearer.

- Applied npm audit fix to updates across multiple dependencies to address security vulnerabilities and maintenance updates.

[Copilot]

Pull request overview

Copilot reviewed 16 out of 18 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (3)

tests/blob/startupErrorRecovery.test.ts:97

• This test uses a fixed port (11001) which is heavily reused across the queue/blob test suites. Since Promise.race() doesn't cancel server.start(), late startup after the timeout can cause flaky port collisions. Prefer port 0 (ephemeral) here.

      11001,

tests/blob/startupErrorRecovery.test.ts:156

• This test uses a fixed port (11002) which is also used by other test suites. If server.start() continues after a Promise.race() timeout, it can start listening later and collide with other tests. Prefer port 0 (ephemeral) here.

      11002,

tests/queue/startupErrorRecovery.test.ts:89

• Even though 11003 is less commonly used, using a fixed port here still risks collisions if tests are ever run concurrently or if a timed-out server.start() continues in the background. Prefer port 0 (ephemeral) for stability.

      11003,

[Copilot]

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 17 out of 19 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 18 out of 20 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 18 out of 20 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (1)

src/blob/SqlBlobServer.ts:116

• In the GC critical error handler, JSON.stringify(error) will usually log {} when error is an Error instance, losing the message/stack in Azurite logs (console gets it, but logger output becomes unhelpful). Log the error message + stack explicitly (and keep the console output if desired).

      (error) => {
        // tslint:disable-next-line:no-console
        console.log(BEFORE_CLOSE_MESSAGE_GC_ERROR, error);
        logger.info(BEFORE_CLOSE_MESSAGE_GC_ERROR + JSON.stringify(error));