Note. This file includes breaking changes after 3.0.0-preview. For legacy Azurite changes, please goto GitHub releases.

• [Breaking] The Linux Docker image no longer includes npm. Node.js and the existing JavaScript entrypoints remain available, so azurite, azurite-blob, azurite-queue, and azurite-table continue to work unchanged. Impact: Images derived from Azurite can no longer run npm commands; install build tooling in a separate build stage instead.

• [Breaking] Raised the minimum supported Node.js runtime to 21+. Support for Node.js 14, 16, 18 and 20 has been removed.
• [Breaking] Migrated the Windows/Linux binary build process from pkg/pkg-fetch to Node.js SEA (Single Executable Applications) using esbuild and postject. Building binaries now requires a Node.js version that supports SEA.
• [Breaking] Removed the deprecated azure-storage dependency. Internal usage and test suites have been migrated to modern Azure SDK clients (@azure/data-tables, @azure/storage-blob, @azure/storage-queue, @azure/identity).
• [Breaking] Standardized binary data handling on Uint8Array instead of Buffer (e.g. MD5 hashes, Content-MD5, internal buffer conversions). Consumers relying on Buffer-specific behavior may need to adjust.
• [Breaking] Removed the default value for the BlobSequenceNumber parameter in the Swagger definition.

• [Breaking] Remove support in table API Azure Pipeline for old node js versions. This means that all table tests will run based on following versions of node js: 14, 16
• [Breaking] Test matrix in Azure Pipeline has removed nodejs 8.
• [Breaking] Batch responses include 3 CRLFs when closing final changesetresponse section to support Go SDK

• [Breaking] Remove the support of DNS name with multiple blocks but without account name, like "http://foo.bar.com:10000/devstoreaccount1/container".
  • When use DNS name with multiple blocks, storage account name must be in the first block, like "http://devstoreaccount1.blob.localhost:10000/container"

• [Breaking] By default Azurite will block requests with unsupported headers or parameters which may impact data integrity.
  • Skip this by switching to loose mode by Azurite configuration parameter --loose.
• [Breaking] Azurite updates underline metadata schema which does not compatible with previous versions.
  • This version cannot guarantee compatible with persisted database models file by previous version. Remove previous metadata file and restart Azurite in case any errors.

• [Breaking] This version cannot guarantee compatible with persisted database models file by previous version. Remove previous metadata file and restart Azurite in case any errors.