emdash-cms/emdash @emdash-cms/cloudflare@1.0.1-rc.0

on GitHub

Patch Changes

• #3515 d274172 Thanks @ascorbic! - Releases EmDash 1.0. This release includes breaking changes, such as removing APIs deprecated during 0.x. The other entries for this version describe each one and how to migrate; check them before upgrading from 0.42.

  From this release, breaking changes ship only in a new major version.

  The first 1.x version is 1.0.1. npm also lists a deprecated emdash@1.0.0, published by mistake from 0.7-era code; do not install it.

• #3518 bc54886 Thanks @ascorbic! - Moves the subpaths that only EmDash itself loads under emdash/internal/, and the D1 and Hyperdrive migration executors under @emdash-cms/cloudflare/internal/. These paths are not public API: their exports can change or be removed in any release.

  Sites that use emdash() in astro.config.mjs need no changes. The integration, the database, cache and media adapter helpers, and the first-party Cloudflare, workerd sandbox and plugin-test packages all load the new paths automatically.

  The following subpaths are removed:

  Removed subpath	Now loaded from
  emdash/routes/*	emdash/internal/routes/*
  emdash/middleware/auth	emdash/internal/middleware/auth
  emdash/middleware/redirect	emdash/internal/middleware/redirect
  emdash/middleware/request-context	emdash/internal/middleware/request-context
  emdash/middleware/setup	emdash/internal/middleware/setup
  emdash/middleware/media-usage-write-fence	emdash/internal/middleware/media-usage-write-fence
  emdash/image-endpoint	emdash/internal/image-endpoint
  emdash/media/local-runtime	emdash/internal/media/local-runtime
  emdash/object-cache/memory	emdash/internal/object-cache/memory
  emdash/db/sqlite-migrations	emdash/internal/db/sqlite-migrations
  emdash/db/libsql-migrations	emdash/internal/db/libsql-migrations
  emdash/db/postgres-migrations	emdash/internal/db/postgres-migrations
  emdash/database/migration-lock	emdash/internal/database/migration-lock
  emdash/database/pg-migration-lock	emdash/internal/database/pg-migration-lock
  emdash/plugins/host	emdash/internal/plugins/host
  emdash/plugins/http-wire	emdash/internal/plugins/http-wire
  emdash/plugins/adapt-sandbox-entry	emdash/internal/plugins/adapt-sandbox-entry
  emdash/plugin-test-runtime	emdash/internal/plugin-test-runtime
  emdash/testing/registry	emdash/internal/testing/registry
  @emdash-cms/cloudflare/db/d1-migrations	@emdash-cms/cloudflare/internal/db/d1-migrations
  @emdash-cms/cloudflare/db/hyperdrive-migrations	@emdash-cms/cloudflare/internal/db/hyperdrive-migrations

  What should I do?

  If your project or package imports one of the removed subpaths directly, replace the import with a public entrypoint:

  • To configure a database, object cache or media provider, use sqlite(), libsql() or postgres() from emdash/db, memoryCache() from emdash/astro, or localMedia() from emdash/media, instead of writing their entrypoints by hand.
  • To test a plugin, use @emdash-cms/plugin-test instead of emdash/plugin-test-runtime.
  • To run your own middleware before EmDash's, set the middleware.outer option of emdash(). The internal auth, setup, redirect and request-context middleware have no public replacement.

  Rebuild after upgrading. emdash migrate rejects a migration manifest written by an earlier EmDash version.

• #3519 0b4be2c Thanks @ascorbic! - Removes the deprecated cloudflareCache() route-cache provider and its @emdash-cms/cloudflare/cache and @emdash-cms/cloudflare/cache/config entry points. Sites that still import cloudflareCache fail to build after upgrading.

  Switch to native Workers Caching with the Astro Cloudflare adapter's provider. The adapter enables Workers Cache in the generated deployment configuration when this provider is set:

  - import { cloudflareCache } from "@emdash-cms/cloudflare";
  + import { cacheCloudflare } from "@astrojs/cloudflare/cache";
  
   export default defineConfig({
   	cache: {
  -		provider: cloudflareCache(),
  +		provider: cacheCloudflare(),
   	},
   });

  Invalidation moves to cache.purge() from cloudflare:workers, so the CF_ZONE_ID and CF_CACHE_PURGE_TOKEN secrets are no longer needed and can be deleted. The KV object cache (kvCache() and @emdash-cms/cloudflare/cache/kv) is unchanged.

• #3519 0b4be2c Thanks @ascorbic! - Adds a startup warning when an installed or configured plugin declares deprecated capability names such as read:content, network:fetch or page:inject. The warning appears once per plugin and lists each current replacement, for example read:content → content:read. The deprecated names keep working throughout 1.x. If a plugin you use triggers the warning, update it, or ask its author to publish a version that uses the current names.

  aiSearch() from @emdash-cms/cloudflare now declares content:read, so it no longer triggers the warning.

• Updated dependencies [d274172, bc54886, 0b4be2c, 0b4be2c, 0b4be2c, 0b4be2c]:

  • emdash@1.0.1-rc.0