chore: Prepare 0.8 (#528)

Author: kylebarron

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+## [0.8.0] - 2025-08-07
+
+### What's Changed
+
+- **Breaking:** Don't double percent-encode paths by @kylebarron in https://github.com/developmentseed/obstore/pull/524
+  - This changes the internals from using [`Path` "encoding"](https://docs.rs/object_store/latest/object_store/path/struct.Path.html#encode) to [`Path` "parsing"](https://docs.rs/object_store/latest/object_store/path/struct.Path.html#parse). This avoids issues where paths could be unintentionally double-encoded. But this means that the user must ensure that paths are valid.
+- fix: Only SHA256 is supported for S3 checksum algorithm by @kylebarron in https://github.com/developmentseed/obstore/pull/527
+
 ## [0.7.3] - 2025-08-01
 
 ### What's Changed

Cargo.lock

@@ -6,4 +6,9 @@ Various integrations with external libraries exist:
 - [`fsspec`](https://github.com/fsspec/filesystem_spec): Use the [`obstore.fsspec`][obstore.fsspec] module.
 - [`zarr-python`](https://zarr.readthedocs.io/en/stable/): Use [`zarr.storage.ObjectStore`](https://zarr.readthedocs.io/en/stable/user-guide/storage.html#object-store), included as of Zarr version `3.0.7` and later. See also the [Obstore-Zarr example](../examples/zarr.md).
 
+And obstore is used internally in more projects:
+
+- [litData](https://github.com/Lightning-AI/litData)
+- [VirtualiZarr](https://github.com/zarr-developers/VirtualiZarr)
+
 Know of an integration that doesn't exist here? [Edit this document](https://github.com/developmentseed/obstore/edit/main/docs/integrations.md).

docs/integrations/index.md

@@ -1,6 +1,6 @@
 [package]
 name = "obstore"
-version = "0.7.3"
+version = "0.8.0"
 authors = { workspace = true }
 edition = { workspace = true }
 description = "The simplest, highest-throughput interface to Amazon S3, Google Cloud Storage, Azure Blob Storage, and S3-compliant APIs like Cloudflare R2."