Skip to content

chore: release 1.0.0-rc.13 - #185

Merged
aesslinger merged 1 commit into
mainfrom
chore/release-1.0.0-rc.13
Oct 29, 2026
Merged

aesslinger merged 1 commit into
mainfrom
chore/release-1.0.0-rc.13

Conversation

@aesslinger

Copy link
Copy Markdown
Collaborator

Bumps version to 1.0.0-rc.13 in Cargo.toml, Cargo.lock, .tabularium, and CHANGELOG.md.

Included since rc.12

Fixed

Dependencies

Docs

Verification

This is a version-bump + CHANGELOG commit (no behavior change). All four component PRs (#180, #184, #182, #183) landed green on CI. Pre-release local DB verification on the post-merge main (the part CI can't give — client_live_tests isn't in CI):

Bumps version to 1.0.0-rc.13 in Cargo.toml, Cargo.lock, .tabularium, and
CHANGELOG.md.

### Included since rc.12

**Fixed:**
- A `prepare` failure inside an open transaction no longer cascades to a
  confusing 25P02 on every subsequent statement in the same session (#170,
  #180). The fix gates the `.ok()` prepare-swallow on `in_transaction`:
  inside an open transaction it short-circuits (ROLLBACK + surface the
  prepare's real SQLSTATE + signal `txn_aborted=true`); outside a transaction
  the recoverable swallow is preserved (a 42P05 on a real PgBouncer bare
  batch). The error message tells the user the transaction was rolled back.
- A `query_typed`/`execute_typed` runtime error inside an open transaction
  no longer re-pins the aborted connection and 25P02-cascades the next
  statement (#181, #184). The sibling of #170 from a different source:
  classifies on the error's `as_db_error()` (a server `DbError` always
  aborts an open transaction; non-`DbError` conservatively assumed aborted).
  Both error arms ROLLBACK + surface the real error + signal
  `txn_aborted=true`, gated on `transaction_effect(query)` being neither
  `Closes` nor `Chains` so a failed `COMMIT`/`COMMIT AND CHAIN` doesn't get a
  spurious ROLLBACK + notice. Closes the 25P02 cascade end-to-end (#170
  prepare-failure + #181 runtime-error = the two faces).

**Dependencies:**
- `uuid` 1.28.0 → 1.29.0 (#182). Additive only (versioned `NonNilUuid`
  constructors); the existing `Uuid` API is untouched.
- `tokio` 1.53.3 → 1.54.1 (#183). The 1.54.1 patch reverts the only
  `time`-subsystem change from 1.54.0, so `tokio::time::timeout` behavior is
  back to 1.53.3-equivalent — the bound the #170/#181 fixes rely on. MSRV
  bumped to 1.85.

**Docs:**
- Centered the PostgreSQL banner, converted to PNG; fixed a stale Tabularis
  logo URL (#179).
@aesslinger aesslinger added the prerelease:rc Version suggestion targets a release candidate label Oct 29, 2026
@aesslinger aesslinger self-assigned this Oct 29, 2026
@kilo-code-bot

kilo-code-bot Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Version bump to 1.0.0-rc.13 is consistent across Cargo.toml, Cargo.lock, .tabularium, and CHANGELOG.md. The only remaining rc.12 reference is the historical changelog heading. The new changelog entry matches the PR description, and no code changes are included.

Files Reviewed (4 files)
  • .tabularium
  • CHANGELOG.md
  • Cargo.lock
  • Cargo.toml

Reviewed by claude-sonnet-5.5 · Input: 250 · Output: 1.5K · Cached: 176.6K

@aesslinger
aesslinger merged commit 96e578b into main Oct 29, 2026
8 of 9 checks passed
@aesslinger
aesslinger deleted the chore/release-1.0.0-rc.13 branch October 29, 2026 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prerelease:rc Version suggestion targets a release candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant