v1.16.0

Added

• RangeReadableStorage — an optional interface a StoragePort implements
  to report an object's size() and open part of it with readRange().
  readStream() was the only read the port declared, and on S3 it returns a
  network body that can be neither stat'ed nor seeked, so a consumer honouring
  Range (a PDF reader paging a large document) served ranges on the local
  driver and silently sent whole objects on S3. Checked with instanceof, like
  DriverAware, so existing StoragePort fakes need no change; a consumer
  falls back to readStream() when the bound port does not implement it.

What's Changed

🔄 Other Changes

• chore(homebrew): point the formula at v1.15.0 by @hakeemRash in #171
• release: v1.16.0 — RangeReadableStorage, so storage consumers can serve ranges on S3 by @hakeemRash in #172

Full Changelog: v1.15.0...v1.16.0