chore: bump MSRV of zarrs to 1.82

I've never clarified an MSRV policy for `zarrs`, but have kept the MSRV >6 months behind the latest release for some time. But, `zarrs` is probably going to use 1.85 not long after it is released, same with 1.86 if trait upcasting stabilises.

.github/workflows/ci.yml

@@ -18,7 +18,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        toolchain: ["stable", "1.77", "beta", "nightly"]
+        toolchain: ["stable", "1.82", "beta", "nightly"]
         features: ["--features \"\"", "--all-features", "--no-default-features"]
     runs-on: ubuntu-latest
     steps:

CHANGELOG.md

@@ -34,6 +34,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Bump `itertools` to 0.14
 - Indicate that `zfp` / `zfpy` codecs have different metadata in codec table
 - Use `zarr-python` 3.0.0 in compatibility tests
+- **Breaking**: Bump MSRV to 1.82 (17 October, 2024)
 
 ### Removed
 - Remove support for pcodec `Try{FloatMult,FloatQuant,IntMult}` mode specs

zarrs/Cargo.toml

@@ -3,7 +3,7 @@ name = "zarrs"
 version = "0.19.0-dev"
 authors = ["Lachlan Deakin <[email protected]>"]
 edition = "2021"
-rust-version = "1.77"
+rust-version = "1.82"
 description = "A library for the Zarr storage format for multidimensional arrays and metadata"
 homepage = "https://zarrs.dev"
 documentation = "https://docs.rs/zarrs"