Skip to content

release: v0.6.20 — pgrx 0.19.1 + PostgreSQL 18 (resolve E-006)#65

Merged
styk-tv merged 1 commit into
mainfrom
release-v0.6.20
Jul 16, 2026
Merged

release: v0.6.20 — pgrx 0.19.1 + PostgreSQL 18 (resolve E-006)#65
styk-tv merged 1 commit into
mainfrom
release-v0.6.20

Conversation

@styk-tv

@styk-tv styk-tv commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Release cut for v0.6.20 — the pgrx 0.16.1 → 0.19.1 + PostgreSQL 18 upgrade (#63, merged in #64).

Version bump + CHANGELOG fold only; no code change beyond the version strings:

  • Cargo.toml / Cargo.lock / pgrdf.control / META.json (both fields) → 0.6.20
  • upgrade bridge renamed → sql/pgrdf--0.5.1--0.6.20.sql (no schema delta)
  • compose.yml SQL mount + regression smoke golden → 0.6.20
  • CHANGELOG.md [Unreleased][0.6.20]

Once CI is green this is ready to tag v0.6.20 (annotated, naming the version), which drives release.yml (pg18 artifacts) → oci-publish.yml (boot+version gate → attest) → update-latest-md.yml.

No schema change, no query-surface change — validated end-to-end on PG 18.4 in #64 (full pgrx test suite + compose regression + W3C harnesses all green). Refs #63.

Version bump + CHANGELOG fold for the v0.6.20 cut:
- Cargo.toml / Cargo.lock / pgrdf.control / META.json (both fields) -> 0.6.20
- rename upgrade bridge -> sql/pgrdf--0.5.1--0.6.20.sql (NO schema delta)
- compose SQL mount + regression smoke golden -> 0.6.20
- fold CHANGELOG [Unreleased] -> [0.6.20]

No schema change and no query-surface change — a build/runtime migration
only (pgrx 0.16.1 -> 0.19.1, PG 18), validated end-to-end on PG 18.4 via #64
(full pgrx test suite + compose regression + W3C harnesses all green).

Refs #63
@styk-tv styk-tv added this to the v0.6.20 milestone Jul 16, 2026
@styk-tv
styk-tv merged commit f9e7fab into main Jul 16, 2026
4 checks passed
@styk-tv
styk-tv deleted the release-v0.6.20 branch July 16, 2026 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant