Skip to content

emdash

[email protected] scope: emdash Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 25d Productivity & Wikis
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

astro cms emdash typescript

Affected surfaces

auth deps

Summary

AI summary

Updates Patch Changes, Minor Changes, and https://github.com/swissky across a mixed release.

Full changelog

Minor Changes

  • #1707 e4eab4f Thanks @swissky! - Brands the admin with the site's own title when no build-time admin.siteName is configured. The admin sidebar previously always showed "EmDash", so operators running several EmDash backends couldn't tell them apart at a glance. The manifest now falls back to the Site Title (Settings → General, then the title captured during setup), WordPress-style. An explicit admin.siteName still wins, and sites with neither keep the "EmDash" default.

  • #1711 386faf5 Thanks @ascorbic! - Excluding sample content when seeding (emdash seed --no-content, or unchecking "Include sample content" in the setup wizard) now also skips the seed's sample bylines and taxonomy terms, so a schema-only setup starts with no sample data at all. Taxonomy definitions, collections, menus, and other structure are still applied. The dev-only setup bypass endpoint accepts ?content=0 to do the same.

Patch Changes

  • #1284 7422460 Thanks @eyupcanakman! - Fixes statically-sandboxed plugins (registered via sandboxed: [] in astro.config.mjs) being absent from the admin Plugins screen. They are now listed alongside trusted and marketplace plugins, and can be fetched, enabled, and disabled through the same plugin management API.

  • #1387 46ef945 Thanks @auggernaut! - Adds LiveSearch route templates and search page navigation options.

  • #1388 cff8498 Thanks @auggernaut! - Fixes public LiveSearch autocomplete requests being blocked by auth middleware.

  • #1708 dea8210 Thanks @swissky! - Fixes slug-change 301 auto-redirects not being created for published entries in revision-supporting collections. Editing a published entry's slug in the admin stages the change as _slug inside a draft revision; on "Publish", ContentRepository.publish() synced the new slug straight into the content table — bypassing handleContentUpdate, the only place auto-redirects were created. Since collections support drafts + revisions by default, the advertised "Auto: slug change" redirect effectively never fired for the standard editing flow, silently breaking old URLs. Publishing now leaves a 301 from the old URL behind whenever an already-published entry's slug changes. First publishes are excluded (a draft's URL was never public), and direct API slug updates behave as before.

  • #1702 90ffe40 Thanks @MA2153! - Restores the idx_content_taxonomies_term index on SQLite/D1 installs that lost it when migration 036 was retried after a partial apply, so taxonomy reverse-lookups are indexed again. The index is now recreated unconditionally during 036 to prevent the same loss on any future partial apply.

  • #1710 2a7063a Thanks @ascorbic! - Fixes MCP tools and content writes failing in Cloudflare dev servers with The file does not exist at ".../deps_ssr/..." after Vite re-optimizes dependencies, which previously required a dev server restart. Also pre-bundles the migration runner, image transform endpoint, and astro/zod so the first setup, image, or content request no longer triggers a mid-session re-optimization and worker reload.

  • Updated dependencies [8a93e1d]:

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track emdash

Get notified when new releases ship.

Sign up free

About emdash

All releases →

Related context

Related tools

Earlier breaking changes

Beta — feedback welcome: [email protected]