emdash-cms/emdash emdash@0.17.2

on GitHub

Patch Changes

• #1356 4e11daa Thanks @ascorbic! - Scope Postgres table/column introspection to the connection's active schema instead of hardcoding public. tableExists and listTablesLike (database/dialect-helpers.ts) and two idempotency checks in the 019_i18n migration queried information_schema with table_schema = 'public', so a Postgres deployment using a non-public schema (per-tenant or shared-cluster setups) would see tables from the wrong schema or none at all, causing collection/schema operations to misbehave and the i18n migration to skip its column additions. These now use current_schema(), matching the already-correct indexExists/columnExists helpers and migration 038.

• #1167 fe6bc78 Thanks @abhishekshankar! - fix(seo): buildMediaUrl handles root-relative paths without doubling the API prefix

• #1345 80f2925 Thanks @scottbuscemi! - Fix frontend pages redirecting to /_emdash/admin/setup on a fully set-up site. The anonymous fast-path "setup probe" in the Astro middleware queries _emdash_migrations to detect a fresh, un-migrated database, but its catch block treated every error as "fresh install" — so a transient DB failure (D1 connection loss, replica unavailable, query timeout, cold-start race, locked SQLite) wrongly bounced real visitors to the setup wizard. The probe now only redirects when the error is a genuinely-missing table (via the shared isMissingTableError helper) and otherwise renders the page normally. The setupVerified flag is also moved onto a globalThis Symbol.for singleton so it isn't duplicated across SSR chunks, which had caused the probe to re-run far more often than intended (and each re-run was another chance to hit the bug).

• Updated dependencies [4ee75f8]:

  • @emdash-cms/admin@0.17.2
  • @emdash-cms/auth@0.17.2
  • @emdash-cms/gutenberg-to-portable-text@0.17.2