Skip to content

Bump emdash from 0.1.0 to 0.24.1#22

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/emdash-0.24.1
Open

Bump emdash from 0.1.0 to 0.24.1#22
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/emdash-0.24.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown

Bumps emdash from 0.1.0 to 0.24.1.

Release notes

Sourced from emdash's releases.

emdash@0.24.1

Patch Changes

  • #1646 c962929 Thanks @​mvanhorn! - Fixes hierarchical taxonomy terms losing their parent in translated locales. A child term now stores its parent's translation group instead of a locale-bound row id, so translating a parent automatically re-nests its existing children in every locale instead of flattening them to the root. A forward-only migration backfills existing parent links.

  • #1644 d64c961 Thanks @​masonjames! - Fixes React 19 development console warnings from the visual editing toolbar's useSyncExternalStore dependency path.

  • Updated dependencies []:

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

emdash@0.24.0

Minor Changes

  • #1577 79fc8b5 Thanks @​marcusbellamyshaw-cell! - Adds offset pagination to getEmDashCollection for numbered archive routes

    getEmDashCollection now accepts an offset option alongside limit, so you can render numbered archive URLs like /page/2 or /tag/security/page/3 without walking cursors or over-fetching from the start:

    const perPage = 20;
    const { entries, hasMore } = await getEmDashCollection("posts", {
    	limit: perPage,
    	offset: (page - 1) * perPage,
    	orderBy: { published_at: "desc" },
    });

    Results now include a hasMore boolean whenever limit is set, so you can show a "next page" link without an extra count query. offset is ignored when a cursor is supplied — cursor (keyset) pagination still wins.

Patch Changes

  • #1558 e659a5c Thanks @​marcusbellamyshaw-cell! - Fixes EmDash overriding security headers set by the host site (#1393). The baseline X-Content-Type-Options, Referrer-Policy, and Permissions-Policy headers were applied unconditionally, overwriting stricter values a host had already set on its own routes. These headers are now applied only when the host hasn't set them — matching the existing Content-Security-Policy behavior — so a host's own values win while EmDash still provides defaults when none are set.

  • #1636 d8487f9 Thanks @​MA2153! - Fixes ctx.cron being undefined during astro dev under the @astrojs/cloudflare adapter, which silently prevented plugins from scheduling cron tasks and stopped the cron hook from ever firing in local dev. The in-process scheduler now keys off Astro's command rather than Vite's, so plugin cron, scheduled publishing, and cleanup run again.

  • Updated dependencies [f5566e8, d063b51, 43a70d4]:

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

emdash@0.23.0

Minor Changes

  • #1349 bd6cc3a Thanks @​MA2153! - Breaking: generated TypeScript interface names in emdash-env.d.ts now derive from the collection slug (singularized) instead of labelSingular. This fixes invalid identifiers (labels with spaces/punctuation) and duplicate identifiers (two collections sharing a label), while keeping names singular so each interface reads as a single entry (slug postsPost, blog_postsBlogPost). Interfaces are renamed wherever the old label-derived name differed from the slug. Users should regenerate emdash-env.d.ts (emdash types or dev-server start) and update any direct interface references in their code.

Patch Changes

  • #1593 b4d7228 Thanks @​ascorbic! - Fixes the admin stylesheet leaking onto public routes in astro dev. The compiled Kumo/Tailwind theme was injected into every page's <head>, overriding host :root tokens (--text-base, --text-lg, ...) and styling otherwise-unstyled pages. The admin shell now loads its stylesheet as a route-scoped <link>, so public routes are unaffected — matching production behaviour.

... (truncated)

Changelog

Sourced from emdash's changelog.

0.24.1

Patch Changes

  • #1646 c962929 Thanks @​mvanhorn! - Fixes hierarchical taxonomy terms losing their parent in translated locales. A child term now stores its parent's translation group instead of a locale-bound row id, so translating a parent automatically re-nests its existing children in every locale instead of flattening them to the root. A forward-only migration backfills existing parent links.

  • #1644 d64c961 Thanks @​masonjames! - Fixes React 19 development console warnings from the visual editing toolbar's useSyncExternalStore dependency path.

  • Updated dependencies []:

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

0.24.0

Minor Changes

  • #1577 79fc8b5 Thanks @​marcusbellamyshaw-cell! - Adds offset pagination to getEmDashCollection for numbered archive routes

    getEmDashCollection now accepts an offset option alongside limit, so you can render numbered archive URLs like /page/2 or /tag/security/page/3 without walking cursors or over-fetching from the start:

    const perPage = 20;
    const { entries, hasMore } = await getEmDashCollection("posts", {
    	limit: perPage,
    	offset: (page - 1) * perPage,
    	orderBy: { published_at: "desc" },
    });

    Results now include a hasMore boolean whenever limit is set, so you can show a "next page" link without an extra count query. offset is ignored when a cursor is supplied — cursor (keyset) pagination still wins.

Patch Changes

  • #1558 e659a5c Thanks @​marcusbellamyshaw-cell! - Fixes EmDash overriding security headers set by the host site (#1393). The baseline X-Content-Type-Options, Referrer-Policy, and Permissions-Policy headers were applied unconditionally, overwriting stricter values a host had already set on its own routes. These headers are now applied only when the host hasn't set them — matching the existing Content-Security-Policy behavior — so a host's own values win while EmDash still provides defaults when none are set.

  • #1636 d8487f9 Thanks @​MA2153! - Fixes ctx.cron being undefined during astro dev under the @astrojs/cloudflare adapter, which silently prevented plugins from scheduling cron tasks and stopped the cron hook from ever firing in local dev. The in-process scheduler now keys off Astro's command rather than Vite's, so plugin cron, scheduled publishing, and cleanup run again.

  • Updated dependencies [f5566e8, d063b51, 43a70d4]:

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

0.23.0

Minor Changes

  • #1349 bd6cc3a Thanks @​MA2153! - Breaking: generated TypeScript interface names in emdash-env.d.ts now derive from the collection slug (singularized) instead of labelSingular. This fixes invalid identifiers (labels with spaces/punctuation) and duplicate identifiers (two collections sharing a label), while keeping names singular so each interface reads as a single entry (slug postsPost, blog_postsBlogPost). Interfaces are renamed wherever the old label-derived name differed from the slug. Users should regenerate emdash-env.d.ts (emdash types or dev-server start) and update any direct interface references in their code.

Patch Changes

... (truncated)

Commits
  • 7611641 ci: release (#1653)
  • 647cfe4 ci: release (#1629)
  • d64c961 fix(core): silence React 19 external store warning (#1644)
  • c962929 fix: store translation_group in taxonomy parent_id to stop cross-locale paren...
  • e659a5c fix(core): apply baseline security headers set-if-absent so host-set values w...
  • 79fc8b5 fix(core): add offset pagination to getEmDashCollection for numbered archives...
  • d8487f9 fix(core): keep plugin cron alive in astro dev under Cloudflare adapter (#1636)
  • b66f697 ci: release (#1592)
  • 3f3375c fix(tests): isolate Astro dev-server lock per integration suite (#1604) (#1605)
  • d74269d fix(core): event-scoped DB connection for cron, plugin contexts, and media pr...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [emdash](https://github.com/emdash-cms/emdash/tree/HEAD/packages/core) from 0.1.0 to 0.24.1.
- [Release notes](https://github.com/emdash-cms/emdash/releases)
- [Changelog](https://github.com/emdash-cms/emdash/blob/main/packages/core/CHANGELOG.md)
- [Commits](https://github.com/emdash-cms/emdash/commits/emdash@0.24.1/packages/core)

---
updated-dependencies:
- dependency-name: emdash
  dependency-version: 0.24.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants