@plumbus/core 0.8.0-beta.7 → 0.8.0-beta.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (19) hide show
  1. package/CHANGELOG.md +10 -0
  2. package/dist/.tsbuildinfo +1 -1
  3. package/dist/cli/commands/migrate.d.ts.map +1 -1
  4. package/dist/cli/commands/migrate.js +3 -14
  5. package/dist/cli/commands/migrate.js.map +1 -1
  6. package/dist/cli/commands/run.d.ts.map +1 -1
  7. package/dist/cli/commands/run.js +2 -7
  8. package/dist/cli/commands/run.js.map +1 -1
  9. package/dist/cli/commands/seed.d.ts.map +1 -1
  10. package/dist/cli/commands/seed.js +2 -7
  11. package/dist/cli/commands/seed.js.map +1 -1
  12. package/dist/config/loader.d.ts.map +1 -1
  13. package/dist/config/loader.js +3 -1
  14. package/dist/config/loader.js.map +1 -1
  15. package/dist/data/connection.d.ts +23 -0
  16. package/dist/data/connection.d.ts.map +1 -1
  17. package/dist/data/connection.js +23 -6
  18. package/dist/data/connection.js.map +1 -1
  19. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,15 @@
1
1
  # @plumbus/core changelog
2
2
 
3
+ ## 0.8.0-beta.8 — 2026-10-01
4
+
5
+ ### Fixed
6
+
7
+ - **Connections made from `config.database` honour `ssl`.** The server and worker pool's connection (`connectPostgresDatabase`), `plumbus seed`, `plumbus run`, and `plumbus migrate`'s create-database and reset connections built their postgres.js options without `ssl`, so they connected in plain text even when the configuration asked for TLS — which production always does. A Postgres that requires TLS refused them: Amazon RDS for PostgreSQL 15+ (`rds.force_ssl=1`) answered `28000 … no encryption`, and the worker's startup preflight surfaced it as `Failed query: SELECT lease_owner, lease_expires_at FROM flow_executions LIMIT 0`. All five now take their options from one `postgresConnectionOptions(config.database)`; `ssl: true` negotiates TLS and verifies the server certificate (supply a private CA, e.g. the RDS bundle, with `NODE_EXTRA_CA_CERTS`). Tenant data-plane connections and `migrate apply` already passed `ssl`.
8
+
9
+ ### Changed
10
+
11
+ - **`DATABASE_SSL=false` now turns TLS off in production.** Production still defaults to TLS; an explicit `false` is for a production Postgres without TLS, which the fix above would otherwise stop connecting to (`validateConfig` keeps its `database.ssl should be enabled in production` warning).
12
+
3
13
  ## 0.8.0-beta.7 — 2026-09-27
4
14
 
5
15
  Carries core 0.7.5 and 0.7.6 from `main` into the beta family.