ci: release#1354
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | c4620e1 | Jun 05 2026, 10:42 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-playground | c4620e1 | Jun 05 2026, 10:43 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-demo-cache | c4620e1 | Jun 05 2026, 10:43 AM |
Scope checkThis PR touches 29 files. PRs with a broad scope are harder to review. Please confirm the scope hasn't drifted beyond the intended change. If this scope is intentional, no action needed. A maintainer will review it. If not, please consider splitting this into smaller PRs. See CONTRIBUTING.md for contribution guidelines. |
@emdash-cms/admin
@emdash-cms/auth
@emdash-cms/auth-atproto
@emdash-cms/blocks
@emdash-cms/cloudflare
@emdash-cms/contentful-to-portable-text
emdash
create-emdash
@emdash-cms/gutenberg-to-portable-text
@emdash-cms/plugin-cli
@emdash-cms/plugin-types
@emdash-cms/registry-client
@emdash-cms/registry-lexicons
@emdash-cms/sandbox-workerd
@emdash-cms/x402
@emdash-cms/plugin-ai-moderation
@emdash-cms/plugin-atproto
@emdash-cms/plugin-audit-log
@emdash-cms/plugin-color
@emdash-cms/plugin-embeds
@emdash-cms/plugin-field-kit
@emdash-cms/plugin-forms
@emdash-cms/plugin-webhook-notifier
commit: |
2602307 to
d24b36b
Compare
d24b36b to
c4620e1
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@emdash-cms/admin@0.17.2
Patch Changes
#1305
4ee75f8Thanks @eyupcanakman! - Fixes plugin admin pages showing a Plugin Error when opened from the Plugin Manager. The Settings gear opens a plugin at its root (/plugins/<id>/), but a plugin that registers its page at/settingsrather than/had no page there, so the admin fell through to a 404. Plugin page resolution now resolves the plugin root to the first registered page and treats/settingsand/settings/as the same path, so a single registration works from the Plugin Manager gear and the sidebar regardless of trailing slash.Updated dependencies []:
@emdash-cms/auth-atproto@0.2.13
Patch Changes
@emdash-cms/cloudflare@0.17.2
Patch Changes
4e11daa,fe6bc78,80f2925]:emdash@0.17.2
Patch Changes
#1356
4e11daaThanks @ascorbic! - Scope Postgres table/column introspection to the connection's active schema instead of hardcodingpublic.tableExistsandlistTablesLike(database/dialect-helpers.ts) and two idempotency checks in the019_i18nmigration queriedinformation_schemawithtable_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 usecurrent_schema(), matching the already-correctindexExists/columnExistshelpers and migration038.#1167
fe6bc78Thanks @abhishekshankar! - fix(seo): buildMediaUrl handles root-relative paths without doubling the API prefix#1345
80f2925Thanks @scottbuscemi! - Fix frontend pages redirecting to/_emdash/admin/setupon a fully set-up site. The anonymous fast-path "setup probe" in the Astro middleware queries_emdash_migrationsto detect a fresh, un-migrated database, but itscatchblock 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 sharedisMissingTableErrorhelper) and otherwise renders the page normally. ThesetupVerifiedflag is also moved onto aglobalThisSymbol.forsingleton 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/plugin-embeds@0.1.21
Patch Changes
@emdash-cms/sandbox-workerd@0.1.5
Patch Changes
4e11daa,fe6bc78,80f2925]:@emdash-cms/auth@0.17.2
@emdash-cms/blocks@0.17.2
create-emdash@0.17.2
@emdash-cms/gutenberg-to-portable-text@0.17.2
@emdash-cms/x402@0.17.2
@emdash-cms/fixture-perf-site@0.0.16
Patch Changes
4e11daa,fe6bc78,80f2925]:@emdash-cms/perf-demo-site@0.0.16
Patch Changes
4e11daa,fe6bc78,80f2925]:@emdash-cms/cache-demo-site@0.0.16
Patch Changes
4e11daa,fe6bc78,80f2925]:Try this PR
Open a fresh playground →
A full working EmDash site, deployed from this branch. Each visit gets its own session-scoped sandbox: no login needed and no shared state. Try the admin, edit content, hit the public site.
Tracks
changeset-release/main. Updated automatically when the playground redeploys.