chore(main): release 0.13.0

[Shiro-Raven]

🤖 I have created a release beep boop

0.13.0 (2026-06-18)

✨ Added

• add hierarchical aggregation as alternative to beam search (159c4a7)
• backends: expose noise config fields and validate ExecutionConfig (#90) (5f10796)
• qprog: add quantum natural gradient optimizer and metric estimators (f5a8634)
• qprog: add QUIVER adaptive directional-gradient optimizer (2f68b8c)
• qprog: add SPSA and QN-SPSA optimizers (e8b7a97)
• qprog: add SPSA and QN-SPSA optimizers (d769665)
• qprog: aggregation strategies as first-class objects (927cfc6)
• qprog: aggregation strategies as first-class objects (ea657ec)
• qprog: QNG+QDrift via deterministic per-evaluation sampling (d7c534c)
• qprog: Quantum Natural Gradient (QNG) optimizer (14d9369)
• qprog: QUIVER adaptive directional-gradient optimizer (a3f8bdb)

🐛 Fixed

• circuits: keep build_overlap_meta backward params disjoint from the ansatz (bc8f2fd)
• pipeline: reverse counts endianness in expectation conversion (160b224)
• qprog: address QUIVER review findings (ade6347)
• qprog: address SPSA/QN-SPSA review findings (a477bbf)
• qprog: isolate optimizer RNG and purify pipeline-env building (c399229)
• qprog: keep unseeded QDrift cohort-consistent for QNG (875d4e1)
• resolve review findings across ZNE, QNG, sampling, and counts conversion (c670032)

🔄 Changed

• hamiltonians: compute the QDrift keep/sample split once per batch (2c59220)
• pipeline: add PipelineSet registry and shared run/accounting seam (3555bde)
• pipeline: carry measurement metadata on MetaCircuit (d1f4fae)
• pipeline: clarify cache identifier names (3471e25)
• pipeline: introduce StageOutput as the stage return type (94f14fe)
• qem: extract ZNE into zne.py and derive QEMStage.consumes_dag_bodies (d5ed005)
• qprog: build cost pipelines from a reusable expectation measurement and extract SolutionSamplingMixin (0503927)
• qprog: cache QN-SPSA overlap circuit, reject zero-iteration runs (c9bbc68)
• qprog: split optimizers into a package and harden selection (e9f14e8)

🔧 Internal

• backends: drop xfail from noise config e2e (fe24ddb)
• enable uv package cache in setup-divi (f893bad)
• enable uv package cache in setup-divi (d1a75c7)
• Merge pull request #91 from QoroQuantum/feat/hierarchical-aggregation (927cfc6)
• Merge pull request #92 from QoroQuantum/feat/qng (14d9369)
• Merge pull request #93 from QoroQuantum/feat/spsa (e8b7a97)
• Merge pull request #94 from QoroQuantum/feat/quiver (a3f8bdb)
• update pre-commit hooks to latest and apply Python 3.13 standards (1a57ec3)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

• Bumps the package and Release Please manifest version to 0.13.0.
• Adds the generated 0.13.0 changelog section.
• Keeps the release PR scoped to metadata and changelog updates.

Confidence Score: 5/5

The changes are limited to release metadata and changelog updates.

The modified files are generated release artifacts with no runtime code changes, and there were no code issues identified.

T-Rex Logs

What T-Rex did

• The run recorded the base state with pyproject/importlib/manifest at version 0.12.1 and the 0.12.1 changelog dated 2026-06-09, with CHANGELOG_HAS_0_13_0 set to False.
• The run recorded the head state with pyproject/importlib/manifest at version 0.13.0, the 0.13.0 top changelog dated 2026-06-18, and the top-section flag set to True with visible Added/Fixed/Changed release notes.

_{Ran code and verified through T-Rex}

_{Reviews (4): Last reviewed commit: "chore(main): release 0.13.0" | Re-trigger Greptile}

[greptile-apps]

Update lockfile version The package version was bumped here, but the committed uv.lock still contains the editable qoro-divi package at 0.12.1. This repo commits the lockfile for reproducible installs and CI/setup uses uv sync, so locked installs can continue to resolve project metadata as 0.12.1 while the release metadata says 0.13.0. Please regenerate uv.lock so the locked project metadata matches this release.

Artifacts

Repro: TOML comparison script for pyproject and uv.lock versions

• Contains supporting evidence from the run (text/x-python; charset=utf-8).

Repro: failing version mismatch command output

• Keeps the command output available without making the summary code-heavy.

Repro: uv locked metadata attempt output

• Keeps the command output available without making the summary code-heavy.

_{Ran code and verified through T-Rex}

Prompt To Fix With AI

This is a comment left during a code review.
Path: pyproject.toml
Line: 8

Comment:
**Update lockfile version** The package version was bumped here, but the committed `uv.lock` still contains the editable `qoro-divi` package at `0.12.1`. This repo commits the lockfile for reproducible installs and CI/setup uses `uv sync`, so locked installs can continue to resolve project metadata as `0.12.1` while the release metadata says `0.13.0`. Please regenerate `uv.lock` so the locked project metadata matches this release.

How can I resolve this? If you propose a fix, please make it concise.