[aao-ipr-bot]

🤖 I have created a release beep boop

0.1.0-beta.1 (2026-10-24)

⚠ BREAKING CHANGES

• reporting: the PostgreSQL reporting stores, the row storage providers, the change feed, the ownership-migration helpers and ReliableReportingService.postgres leave adcp; install adcp-reporting-storage[pg] (plus gcs/s3/azure) and import them from adcp_reporting_storage. The adcp[reporting-gcs], [reporting-s3] and [reporting-azure] extras are removed. See docs/reporting-storage-package-migration.md.

Features

• reporting: ship the Reliable Reporting storage as adcp-reporting-storage (#1557) (d59eee9)

Bug Fixes

• reporting-storage: require the adcp release that contains the split (#1577) (a2315b7)

---

This PR was generated with Release Please. See documentation.

[aao-secretariat]

Ladon does not review bot-authored PRs.

[aao-ipr-bot]

🤖 Created releases:

• adcp-reporting-storage-v0.1.0-beta.1

🌻

[bokelley]

Release-process note (ESA feedback): 9.0.0 GA removed the PostgreSQL reporting stores from adcp before this package was installable. For that window, the migration doc's pip install "adcp-reporting-storage[pg]" failed, and Postgres reporting adopters had to stay on 9.0.0b4 until this release published.

To prevent a repeat, #1605 adds a gate to release-publish.yml. An adcp release now builds only if every companion distribution has a published, non-yanked release on PyPI whose adcp requirement accepts the new version. Today 9.1.0 passes with 0.1.0b4, and a future adcp 10.0.0 will wait for a storage release that accepts it.