1.8.0-beta.1 (2026-11-13)
Features Added
- Added support for session authentication. Set
SessiononClientOptionsto configure it. Sessions apply only to
clients authenticated with anazcore.TokenCredential, and only to the file reads they send to the blob endpoint;
requests to the DFS endpoint, writes and every other operation keep using the bearer token. With
SessionOptions.Enabledset to true, reads are authenticated with a session created and cached per file system.
The default, nil, currently resolves to disabled; false disables sessions explicitly.- Each client created with a constructor has its own session cache. Clients derived from it with
service.Client.NewFileSystemClient,filesystem.Client.NewDirectoryClientandfilesystem.Client.NewFileClient
share that cache. Clients created withdirectory.Client.NewFileClientand
directory.Client.NewSubdirectoryClienthave their own cache, so navigating through a directory can create
additional sessions for the same file system. - The account name that signs session requests is derived from the client's URL, or set with
SessionOptions.AccountNamefor a custom domain. When it can be determined from neither, client construction
fails ifSessionOptions.Enabledwas set to true.
- Each client created with a constructor has its own session cache. Clients derived from it with
- Added support for data locality in managed downloads through
LayoutAwareRoutingonfile.DownloadBufferOptions
andfile.DownloadFileOptions. When it is set to true and the initial read carries the service's layout download
hint, the remaining chunks are routed to the endpoint that serves each one. The default, nil, currently resolves to
disabled; false disables it explicitly. When the service can't provide a layout, downloads use the client's
configured endpoint.
Bugs Fixed
- The token credential constructors now return the error from creating their blob client instead of discarding it.
Other Changes
- Updated
azblobversion to1.9.0-beta.1 - Updated
sdk/storage/internalversion to0.2.0-beta.1