From 5d304dd8627c1a0e5beb4aa19ff568731acb1721 Mon Sep 17 00:00:00 2001 From: "gradienthealth-release-please[bot]" <280451564+gradienthealth-release-please[bot]@users.noreply.github.com> Date: Thu, 7 May 2026 18:59:31 +0000 Subject: [PATCH 1/2] chore(main): release 2.0.0 --- .release-please-manifest.json | 2 +- CHANGELOG.md | 7 +++++++ pyproject.toml | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/.release-please-manifest.json b/.release-please-manifest.json index c3f1463..895bf0e 100644 --- a/.release-please-manifest.json +++ b/.release-please-manifest.json @@ -1,3 +1,3 @@ { - ".": "1.2.0" + ".": "2.0.0" } diff --git a/CHANGELOG.md b/CHANGELOG.md index ca05658..d109642 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,12 @@ # Changelog +## [2.0.0](https://github.com/gradienthealth/cloud_optimized_dicom/compare/v1.2.0...v2.0.0) (2026-05-07) + + +### Miscellaneous Chores + +* **PROC-1668:** trigger v2.0.0 release ([#135](https://github.com/gradienthealth/cloud_optimized_dicom/issues/135)) ([a2f2c1a](https://github.com/gradienthealth/cloud_optimized_dicom/commit/a2f2c1a852e6fa8ee714a4db8ca8527f83531814)) + ## [1.2.0](https://github.com/gradienthealth/cloud_optimized_dicom/compare/v1.1.1...v1.2.0) (2026-04-30) diff --git a/pyproject.toml b/pyproject.toml index a13cd46..d3a552f 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "cloud-optimized-dicom" -version = "1.2.0" +version = "2.0.0" description = "A library for efficiently storing and interacting with DICOM files in the cloud" readme = "README.md" authors = [ From 99db908ab8834aa18e798a153087fb674d3fec33 Mon Sep 17 00:00:00 2001 From: Cal Nightingale Date: Thu, 7 May 2026 15:05:56 -0400 Subject: [PATCH 2/2] chore: backfill v2.0.0 changelog with #134's breaking change Release-please failed to parse the squashed `feat!(PROC-1668):` subject from #134 and skipped it, leaving v2.0.0 listing only the trigger chore from #135. This rewrites the entry under the correct BREAKING CHANGES + Features sections so the published changelog reflects the actual user-facing change. Co-Authored-By: Claude Opus 4.7 (1M context) --- CHANGELOG.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d109642..3fdc404 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,9 +3,17 @@ ## [2.0.0](https://github.com/gradienthealth/cloud_optimized_dicom/compare/v1.2.0...v2.0.0) (2026-05-07) -### Miscellaneous Chores +### ⚠ BREAKING CHANGES + +* **PROC-1668:** `cloud_optimized_dicom` now depends on upstream `pydicom>=3.0` instead of the `pydicom3` fork. Downstream impact: + - `isinstance` checks against `pydicom3.*` on cod-returned objects will start returning `False` — switch to `pydicom.*`. (This is exactly the bug PROC-1668 fixes for gradient-beam.) + - Installing `cloud-optimized-dicom` no longer transitively installs `pydicom3`. Code that imported `pydicom3` only because cod brought it in must either switch to `import pydicom` or add the fork to its own dependencies. + - Environments pinned to `pydicom<3` will no longer resolve. Bump to `pydicom>=3.0`. + + +### Features -* **PROC-1668:** trigger v2.0.0 release ([#135](https://github.com/gradienthealth/cloud_optimized_dicom/issues/135)) ([a2f2c1a](https://github.com/gradienthealth/cloud_optimized_dicom/commit/a2f2c1a852e6fa8ee714a4db8ca8527f83531814)) +* **PROC-1668:** drop pydicom3 fork in favor of upstream pydicom ([#134](https://github.com/gradienthealth/cloud_optimized_dicom/pull/134)) ([42d5e7e](https://github.com/gradienthealth/cloud_optimized_dicom/commit/42d5e7eb8110c120a7feb41085a5efc3270ef586)) ## [1.2.0](https://github.com/gradienthealth/cloud_optimized_dicom/compare/v1.1.1...v1.2.0) (2026-04-30)