Releases: google/xarray-beam
Releases · google/xarray-beam
v0.10.1
Update xarray version in docs build PiperOrigin-RevId: 813456305
v0.10.0
Add docs for xbeam.Dataset PiperOrigin-RevId: 813378676
v0.9.3
Update xarray_beam version to 0.9.3. PiperOrigin-RevId: 810535844
v0.9.2
Expose encoding parameter in ChunksToZarr. PiperOrigin-RevId: 806388507
v0.9.1
Adds option to specify zarr format version to ChunksToZarr This allows users to specify the desired Zarr format version (2 or 3) when writing datasets using `xarray_beam`. The default behavior remains unchanged, allowing the underlying zarr library to determine the format. PiperOrigin-RevId: 805225875
v0.9.0
Vendor rechunker.algorithm inside xarray-beam Rechunker is deprecated and no longer maintained: https://github.com/pangeo-data/rechunker/issues/160 In particular, it pins zarr=2, but we need to support zarr v3 in xarray-beam. PiperOrigin-RevId: 804545298
v0.8.1
Switch Xarray-Beam packaging to pyproject.toml This is the modern alternative to setup.py. PiperOrigin-RevId: 804528285
0.8.0: Add xarray_beam.replace_template_dims
PiperOrigin-RevId: 750350345
0.7.0: Add a warning when using xarray_beam.ChunksToZarr with no template
If this works well at some point in the future (e.g., using zarr v3), we can always remove the warning. But for now, this is better than letting users run directly into the race condition in https://github.com/google/xarray-beam/issues/85 I've also removed all suggestions from the docs of omitting a `template`. PiperOrigin-RevId: 728341864
release version 0.6.3
PiperOrigin-RevId: 587056902