NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #3116 most downloaded on PyPI
A file format that achieves a new frontier of IO efficiency
Latest stable
0.8.6
Last release 1 months ago
20 Oct 2026
Release timing varies
gaps range from 2 weeks to 11 months
Most releases are documented
notes for 11 of 16 stable releases
2 versions withdrawn
withdrawn after publishing
4 years old
19 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Reduce GCS QPS on ArrayRecordReader open via ReadLast. by @copybara-service[bot] in https://github.com/google/array_record/pull/212
Full Changelog: https://github.com/google/array_record/compare/v0.8.5...v0.8.6
Update version in MODULE.bazel from 0.8.4 to 0.8.5 to trigger the v0.8.5 PyPI wheel build, GitHub Release, and Bazel Central Registry publication work
Update version in MODULE.bazel from 0.8.4 to 0.8.5 to trigger the v0.8.5 PyPI wheel build, GitHub Release, and Bazel Central Registry publication workflow, incorporating the Intel macOS crc32c BCR compilation fix and the abseil-cpp 20260107.1 upgrade.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Bazel Central Registry's verify_stable_archives check rejects GitHub's dynamic /archive/refs/tags/ tarballs because their gzip metadata is not guarant
Bazel Central Registry's verify_stable_archives check rejects GitHub's dynamic /archive/refs/tags/ tarballs because their gzip metadata is not guaranteed to remain byte-identical across regenerations. Existing google/array_record releases do not attach a static source tarball asset, and cutting a release previously required updating the version in multiple places and manually triggering wheel builds.
Streamline the release pipeline into .github/workflows/publish_release.yml with MODULE.bazel as the single source of truth for the release version:
setup.py to read version directly from MODULE.bazel, eliminating version drift between setup.py and MODULE.bazel.publish_release.yml automatically on pushes to main touching MODULE.bazel (skipping cleanly in ~6s if v${VERSION} already exists), or manually via workflow_dispatch.cut-github-release (which generates a deterministic array_record-v${VERSION}.tar.gz archive via git archive) and publish-bcr (bazel-contrib/publish-to-bcr) behind build-and-publish-wheels so tags and BCR PRs are only created after all platform wheels build and pass tests..github/workflows/publish_release.yml as the entrypoint workflow filename so existing PyPI Trusted Publishing OIDC continues to work without configuration changes.Fix dependency issues and add reading/writing with gs:// URIs
Fix dependency issues and add reading/writing with `gs://` URIs
PiperOrigin-RevId: 831144085
Add Python 3.14 build and deprecate 3.10.
Add Python 3.14 build and deprecate 3.10.
Also:
- fix test issues due to h5py build
- bump version after the last release
PiperOrigin-RevId: 823609303
Revert the last cpp protobuf update and GCS reader support.
Revert the last cpp protobuf update and GCS reader support.
The required riegeli version depends on protobug that is incompatible with TF. Ported from #175
PiperOrigin-RevId: 797851410
ArrayRecord 0.8.0 release. PiperOrigin-RevId: 797435637
ArrayRecord 0.8.0 release.
PiperOrigin-RevId: 797435637
Fix breakage due to rules_cc. PiperOrigin-RevId: 784673657
Fix breakage due to rules_cc.
PiperOrigin-RevId: 784673657
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Publish ArrayRecord 0.4.x->0.5.0 to PyPI.
Publish ArrayRecord 0.4.x->0.5.0 to PyPI.
PiperOrigin-RevId: 575239033
Release ArrayRecord 0.4.1. PiperOrigin-RevId: 554817684
Release ArrayRecord 0.4.1.
PiperOrigin-RevId: 554817684
__getitem__() signature: the method now accepts a single integer and returns a single record, as per Python standard.
__getitem__() signature: the method now accepts a single integer and returns a single record, as per Python standard.__getitems__() allows to query multiple records.__getitem__() signature: Batching indexes is no longer required for good performance. Accessing elements can be done in Python:
Changelog:
__getitem__() signature: Batching indexes is no longer required for good performance. Accessing elements can be done in Python:[source[i] for i in range(...)]
Added Python DataSource class for handling set of files conveniently.
Changelog:
Nothing published for this version
One column per quarter.