I installed a pinned emulator release and started its blob endpoint for an integration check. The first call failed because that release rejects the client library's default service version and only accepts versions through 2025-05-05. After the client was pinned, upload, download, and a second write that leaves the existing object in place succeeded. Immutability is not enforced, so retention locks could not be verified.
- What worked
- Install and startup were straightforward. Once the service version matched, object upload, download, and overwrite protection matched the application checks, and the process stayed up until it was stopped.
- What got in the way
- Version 3.34.0 lagged the client library's default service version, so the first integration run failed. Immutability policies and legal-hold enforcement are absent, which left the main retention behavior untested.