Bump emdash from 0.1.0 to 0.19.0

[dependabot]

Bumps emdash from 0.1.0 to 0.19.0.

Release notes

Sourced from emdash's releases.

emdash@0.19.0

Minor Changes

• #1442 e96587f Thanks @​ascorbic! - Add status, author, and date-range filtering to the admin content list (#1288). The content list API gains authorId, dateField, dateFrom, and dateTo query params (all additive and optional), and a new GET /_emdash/api/content/{collection}/authors endpoint lists the distinct authors of a collection's content (gated on content:read). Filtering runs server-side, so it works across the whole collection rather than only the loaded page.

• #1439 023893a Thanks @​ascorbic! - Add content filtering by byline credit. getEmDashCollection now accepts a reserved byline key in where that returns entries credited to a byline in any position, including co-authored entries where the byline is a secondary credit. This makes author archive pages possible without querying the database directly. Pass a single byline translation group or an array to match any of several.

  const byline = await getBylineBySlug("jane-doe");
  const { entries } = await getEmDashCollection("posts", {
  	where: { byline: byline.translationGroup ?? byline.id },
  	orderBy: { published_at: "desc" },
  });

  A getEntriesByByline(collection, byline, options) helper wraps the same filter, mirroring getEntriesByTerm.

• #1367 f41092b Thanks @​MA2153! - Add content-reference database schema: _emdash_relations (relationship-type definitions, row-per-locale) and _emdash_content_references (directed, locale-agnostic edges between content entries linked by translation_group). Additive, forward-only migration 043; no existing tables change. Groundwork for reference fields — no field type, API, or admin UI yet.

• #1438 850c1b7 Thanks @​ascorbic! - Generate responsive srcsets for media rendered with the Image and Portable Text image components. EmDash now routes locally/R2-stored media through Astro's configured image service (astro:assets) -- the Cloudflare Images binding on Workers, sharp on Node -- producing width-appropriate candidates and modern formats (e.g. WebP) instead of a single full-size <img>.

  This works automatically:

  • Media served from a configured storage publicUrl (R2 custom domain, S3/CDN) is authorized and optimized.
  • Same-origin proxied media (local storage, or R2 without a public URL) is optimized when siteUrl is set; the matching image.remotePatterns entry is registered for you, scoped to the media route.
  • In astro dev it works out of the box without configuration.

  When optimization isn't possible (no image service available, an unauthorized host, or unknown dimensions) the components fall back to a plain <img>, so existing sites keep rendering exactly as before. No template changes are required.

• #1312 c39789c Thanks @​ascorbic! - Drive scheduled publishing from a real heartbeat instead of request side effects (#1303).

  Content scheduled via the admin now actually transitions to published when its time arrives. Previously nothing promoted the row — status stayed scheduled and published_at stayed null forever.

  A new sweep (publishDueContent) promotes due content and runs alongside the existing cron tick and system cleanup:

  • Node / single-process: the timer-based scheduler already drives it — no action needed.
  • Cloudflare Workers: a scheduled() handler driven by a Cron Trigger now runs the sweep. The request-driven PiggybackScheduler is gone, so there are no maintenance side effects on visitor requests.

  @emdash-cms/cloudflare ships a Worker entry that wraps Astro's handler with the scheduled() handler (@emdash-cms/cloudflare/worker, plus createScheduledHandler() for hand-assembled Workers). When a cache provider is configured, the handler also purges edge-cache tags for whatever it published, so stale snapshots produced before the scheduled time are evicted.

  Migration for existing Cloudflare sites. New sites get this from the templates. Existing deployments must update two files:

  // src/worker.ts
  export { default, PluginBridge } from "@emdash-cms/cloudflare/worker";

  // wrangler.jsonc
  "triggers": { "crons": ["* * * * *"] }

... (truncated)

Changelog

Sourced from emdash's changelog.

0.19.0

Minor Changes

• #1442 e96587f Thanks @​ascorbic! - Add status, author, and date-range filtering to the admin content list (#1288). The content list API gains authorId, dateField, dateFrom, and dateTo query params (all additive and optional), and a new GET /_emdash/api/content/{collection}/authors endpoint lists the distinct authors of a collection's content (gated on content:read). Filtering runs server-side, so it works across the whole collection rather than only the loaded page.

• #1439 023893a Thanks @​ascorbic! - Add content filtering by byline credit. getEmDashCollection now accepts a reserved byline key in where that returns entries credited to a byline in any position, including co-authored entries where the byline is a secondary credit. This makes author archive pages possible without querying the database directly. Pass a single byline translation group or an array to match any of several.

  const byline = await getBylineBySlug("jane-doe");
  const { entries } = await getEmDashCollection("posts", {
  	where: { byline: byline.translationGroup ?? byline.id },
  	orderBy: { published_at: "desc" },
  });

  A getEntriesByByline(collection, byline, options) helper wraps the same filter, mirroring getEntriesByTerm.

• #1367 f41092b Thanks @​MA2153! - Add content-reference database schema: _emdash_relations (relationship-type definitions, row-per-locale) and _emdash_content_references (directed, locale-agnostic edges between content entries linked by translation_group). Additive, forward-only migration 043; no existing tables change. Groundwork for reference fields — no field type, API, or admin UI yet.

• #1438 850c1b7 Thanks @​ascorbic! - Generate responsive srcsets for media rendered with the Image and Portable Text image components. EmDash now routes locally/R2-stored media through Astro's configured image service (astro:assets) -- the Cloudflare Images binding on Workers, sharp on Node -- producing width-appropriate candidates and modern formats (e.g. WebP) instead of a single full-size <img>.

  This works automatically:

  • Media served from a configured storage publicUrl (R2 custom domain, S3/CDN) is authorized and optimized.
  • Same-origin proxied media (local storage, or R2 without a public URL) is optimized when siteUrl is set; the matching image.remotePatterns entry is registered for you, scoped to the media route.
  • In astro dev it works out of the box without configuration.

  When optimization isn't possible (no image service available, an unauthorized host, or unknown dimensions) the components fall back to a plain <img>, so existing sites keep rendering exactly as before. No template changes are required.

• #1312 c39789c Thanks @​ascorbic! - Drive scheduled publishing from a real heartbeat instead of request side effects (#1303).

  Content scheduled via the admin now actually transitions to published when its time arrives. Previously nothing promoted the row — status stayed scheduled and published_at stayed null forever.

  A new sweep (publishDueContent) promotes due content and runs alongside the existing cron tick and system cleanup:

  • Node / single-process: the timer-based scheduler already drives it — no action needed.
  • Cloudflare Workers: a scheduled() handler driven by a Cron Trigger now runs the sweep. The request-driven PiggybackScheduler is gone, so there are no maintenance side effects on visitor requests.

  @emdash-cms/cloudflare ships a Worker entry that wraps Astro's handler with the scheduled() handler (@emdash-cms/cloudflare/worker, plus createScheduledHandler() for hand-assembled Workers). When a cache provider is configured, the handler also purges edge-cache tags for whatever it published, so stale snapshots produced before the scheduled time are evicted.

  Migration for existing Cloudflare sites. New sites get this from the templates. Existing deployments must update two files:

  // src/worker.ts
  export { default, PluginBridge } from "@emdash-cms/cloudflare/worker";

  // wrangler.jsonc
  "triggers": { "crons": ["* * * * *"] }

... (truncated)

Commits

• 0df001e ci: release (#1418)
• c63f9ca fix(core): include term description for flat taxonomies in getTaxonomyTerms()...
• 4809661 feat(core): RelationRepository (content-references data layer) (#1444)
• a4c2af2 fix(core): hydrate taxonomy terms in entry's resolved locale (#1441) (#1445)
• e96587f feat(admin): status, author, and date-range filters for content list (#1288) ...
• 023893a feat: native content filtering by byline credit (#1439)
• 850c1b7 feat: responsive srcset for media via astro:assets (#1438)
• 61ea3c9 fix(seed): honor non-en default locale across export-seed → seed round-trip (...
• f41092b feat(core): content references database schema (#1367)
• c39789c fix(scheduling): drive scheduled publishing from a real heartbeat (#1312)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.