Skip to content

Trellis 0.1.0-beta

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 29 Oct 15:31
· 1114 commits to main since this release
1820fd7

The trellis CLI, and the precompiled builds of the Elixir (trellis_pg) and Ruby (trellis-pg) bindings. See docs/releasing.md.

Several small changes noted below, but the big change is documented, and smaller connection pools for the Trellis clients (including the embedded clients). Each client now has two connection pools, they each lazily establish connections and they each cleanup idle connections after 60sec:

  • Call pool is used for API calls like define and `status. By default this pool can establish up to 20 connections, but it will remain empty until it receives an API call from the client application
  • Background pool is used by staging and drain threads. It will have a maximum size of 2N + 5 where N is the number of drain threads.

What's Changed

  • Packaging hygiene for the alpha: slim crate package, publish flags, stale test shards, release-binary gate (part of #1425) by @mmmries in #1432
  • Trim the trellis crate's public API; public enums and report structs are #[non_exhaustive] (part of #1425) by @mmmries in #1433
  • Purge references to closed issues and PRs outside ADRs; present-tense docs, metrics and environment tables (part of #1425) by @mmmries in #1435
  • catching_up is a reported status, not a stored one: split StoredStatus from TransformStatus; V8 drops the word from the CHECK and triggers (part of #1425) by @mmmries in #1436
  • self_check compares only a definition whose reported status is live; drop plan-history references (closes #1434) by @mmmries in #1437
  • Document what a handle uses: connections, threads and memory by @mmmries in #1469
  • Fewer idle connections: one LISTEN and heartbeat per client, role-sized pools that close when idle, standby staging workers by @mmmries in #1475

Full Changelog: v0.1.0-alpha...v0.1.0-beta