github emdash-cms/emdash @emdash-cms/plugin-cli@0.11.0

latest releases: @emdash-cms/plugin-test@0.1.0, @emdash-cms/sandbox-workerd@0.6.0, @emdash-cms/plugin-embeds@0.1.46...
4 hours ago

Minor Changes

  • #3081 da171b3 Thanks @ascorbic! - Adds repository-level automated plugin releases. emdash-plugin release setup writes one shared .github/workflows/emdash-release.yml at the Git repository root, including when setup runs from a nested package. The workflow resolves <slug>@<version> tags to a unique plugin manifest, rejects version mismatches before attestation, and requests its first repository connection through GitHub OpenID Connect without an Actions secret.

    Prepare later packages with emdash-plugin profile setup --dir <package-directory>. Their first release reuses approved repository workflow scopes when the signed package profile names the same repository. Tag and manual-run scopes accumulate after publisher confirmation instead of replacing each other. Existing package approvals remain package-scoped until the publisher explicitly confirms a repository connection; existing generated workflows and the legacy optional connection-invitation input remain supported.

  • #3081 da171b3 Thanks @ascorbic! - Updates emdash-plugin init to produce a validated, package-manager-aware plugin project. Interactive setup shows the resolved publisher, author, security contact, repository, target, and package manager before writing. Non-interactive setup requires explicit ownership flags unless --use-detected opts into the active publisher session and local Git metadata.

    Generated projects pin the plugin CLI version, use bounded EmDash dependencies, include validation and publishing scripts, and add AGENTS.md with a local creating-plugins skill. .agents/skills and .claude/skills link to the same canonical skill directory, while .claude/CLAUDE.md links to AGENTS.md. pnpm projects include the reviewed esbuild install policy and use an explicit SandboxedPlugin annotation so declaration output remains portable. The scaffolder validates the complete manifest and parent paths before writing and stages new projects atomically.

  • #3084 b581ff8 Thanks @ascorbic! - Adds a workerd-backed Vitest host for sandboxed plugin tests and includes it in projects created by emdash-plugin init. emdashPluginTest() builds the plugin and configures D1, Worker Loader, and the production PluginBridge; createPluginTestHost() invokes hooks and routes through the production sandbox boundary and provides helpers for content fixtures, plugin storage, and KV assertions.

  • #3093 ea2ccd5 Thanks @ascorbic! - Adds Changesets-aware automated plugin releases. emdash-plugin release setup detects a root .changeset/config.json and offers to follow Changesets releases, <slug>@<version> tags, or manual runs. Use --trigger auto|changesets|tags|manual in non-interactive setup.

    The Changesets variant accepts the official Changesets Action published-package JSON through a reusable workflow. It supports mixed monorepos where npm package names differ from EmDash plugin IDs, ignores ordinary npm packages, verifies every reported plugin version, and publishes matching plugins as a matrix. Private EmDash-only packages produce a setup warning unless Changesets versions and tags them.

Patch Changes

  • Updated dependencies [da171b3, befce6d, 4cc150e]:
    • @emdash-cms/registry-client@0.6.0
    • @emdash-cms/registry-lexicons@0.5.0

Don't miss a new emdash release

NewReleases is sending notifications on new releases.