Repository navigation
Description
Tracking issue for the v0.2.3 release. Procedure: prompts/pg_durable-release.md.
This issue is the state + audit trail for the release (checkboxes + links); the
step-by-step procedure lives in the release prompt, not here.
Cut line: head of main @ b4579ae. The v0.2.3 changelog (#245) is merged, and the
## [0.2.3] entry reflects only already-merged work. All other currently-open PRs
(#242, #238, #234, #228, #221, #217, #209, …) are v0.2.4 candidates — none are in
this release.
Tag commit: b4579ae
Published by: Pino de Candia (Pino de Candia (@pinodeca))
Provider-line context
v0.2.3 stays in the duroxide-pg provider compatibility line that began at v0.2.2, so
the upgrade source is v0.2.2 (sql/pg_durable--0.2.2--0.2.3.sql). Schema note: fresh
installs use _duroxide; installs upgraded from ≤ 0.2.2 keep the legacy duroxide
schema, resolved at runtime via df.duroxide_schema() (#201). Upgrade/backward-compat
tests cover both.
Checklist
- Cut line confirmed (head of
main@b4579ae; all other open PRs → v0.2.4) - Changelog merged (PR docs: add v0.2.3 changelog entry #245)
- Version/upgrade-script sanity (
Cargo.toml= 0.2.3,pg_durable.controltemplated,sql/pg_durable--0.2.2--0.2.3.sqlpresent) - CI green on tag commit
b4579ae(Format, Clippy & Tests PG17 + PG18, Example Smoke Checks) - Tagged v0.2.3 → draft Release (Package Release run 27722425453; draft created with PG17/PG18
.deb+ source tarballs + SHA256SUMS — pending publish) - Release published 2026-06-17 (approved by: Pino de Candia / Pino de Candia (@pinodeca); https://github.com/microsoft/pg_durable/releases/tag/v0.2.3)
- GHCR images confirmed (Docker Publish run 27724424343; pushed
0.2.3-pg17/18,v0.2.3-pg17/18, floatingpg17/pg18/latest) - Next-cycle PR opened (chore: start 0.2.4 development cycle #247 — bump
Cargo.toml/Cargo.lockto 0.2.4, empty0.2.3--0.2.4upgrade script,## [0.2.4] - Unreleasedchangelog placeholder)
Activity
docs: add v0.2.3 changelog entry (#245)
pinodeca commentedon Jun 17, 2026
All the release workflow steps are complete. The next-cycle PR (bump version to 0.2.4) hasn't yet merged, but that's no reason to keep this release issue open.
I also want to highlight that this is the 1st release orchestrated by pointing Copilot (with Opus 4.8) to the new version of
prompts/pg_durable-release.md, introduced by #246 (which is still in review).Closing now.
chore: start 0.2.4 development cycle (#247)