Skip to content

Revert new API and restore DBConnection - #412

Merged
ruslandoga merged 3 commits into
masterfrom
rd/ecto-3-14-release-strategy
Aug 8, 2026
Merged

Revert new API and restore DBConnection#412
ruslandoga merged 3 commits into
masterfrom
rd/ecto-3-14-release-strategy

Conversation

@ruslandoga

Copy link
Copy Markdown
Collaborator

What changed

  • Revert new api #341 and restore the DBConnection-based public API on master.
  • Keep compatible work landed after new api #341, including Ecto 3.14, current Decimal and Mint dependencies, RowBinary correctness fixes and optimizations, benchmark cleanup, and CI maintenance.
  • Adapt the later RowBinary integration/property tests to the restored DBConnection query and result APIs.
  • Keep the broader compatibility CI matrix, with explicit ClickHouse and timezone values.

Why

The replacement HTTP pool and breaking public API are not ready to ship yet. Restoring the released DBConnection architecture lets ch publish an Ecto 3.14-compatible release without forcing unrelated API, Elixir, and OTP migrations on users. Development of the new API can continue on a separate branch.

The revert was resolved against current history rather than resetting or rewriting master.

Verification

  • Compared the result with v0.8.3; the DBConnection-era core files match that release, while the remaining diff consists only of intentionally retained maintenance, dependency, RowBinary, and test changes.
  • Confirmed no NimblePool or new Help test-helper references remain.
  • MIX_ENV=test mix format --check-formatted
  • MIX_ENV=test mix compile --warnings-as-errors
  • MIX_ENV=test mix test — 605 passed, 10 skipped, 5 excluded
  • mix deps.unlock --check-unused
  • git diff --check

@ruslandoga
ruslandoga marked this pull request as ready for review August 8, 2026 14:59
@ruslandoga
ruslandoga merged commit 1772132 into master Aug 8, 2026
5 checks passed
@ruslandoga
ruslandoga deleted the rd/ecto-3-14-release-strategy branch August 8, 2026 16:16
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