v0.5.0-beta.5

Prerelease artifacts for the EmDash Registry.

v0.5.0-beta.4

Prerelease artifacts for the EmDash Registry.

v0.4.0

Minor Changes

• #82 0572f9c Thanks @saariuslystoned! - Connect now gives the Payments plugin its own DinkusKit store key, so nothing is pasted: DinkusKit.com hands the key over at the end of Connect, the plugin keeps it in its encrypted Connect setting, and the status page uses it to read payment status. The Store key setting is gone. A missing or unknown key asks for Connect again, and a store whose Commerce plugin is not connected yet is told to connect Commerce first. Needs DinkusKit.com with per-plugin keys deployed first; stores that pasted a key press Connect again once.

v0.3.0

Minor Changes

• #76 7371c80 Thanks @saariuslystoned! - Payment setup page reads payment status with a fresh pass traded from the store key on every load, the way checkout does, so it shows the current answer after its 5-minute DinkusKit sign-in lapses and to every store admin. Paste the store key from DinkusKit.com's Set up Commerce box into the new Store key setting, as for Ship. Sign in again now appears only when Payments isn't connected for the store or a Stripe change (Set up or resume Stripe, provider identity, recovery) needs it; a missing or refused store key is named instead. The hosted Payments Worker accepts the store's checkout pass on GET /v1/status (deploy it before releasing this plugin).

v0.2.10

Patch Changes

• #64 bc44f09 Thanks @saariuslystoned! - Add a disabled-by-default, operator-scoped action that preserves a rejected legacy TEST binding's history and prepares one v2 operation without creating an account. Add explicit confirmation through the existing Registry session; validate and preserve the stored start, matched record and audit digest internally.

v0.2.9

Patch Changes

• #51 c5193c6 Thanks @saariuslystoned! - Implement the locked release-beta-cut-071 release process for @dinkuskit/payments:

  • Accept both the stable (dinkus-payments -> r_3brsc2on3bu673rn) and beta (dinkus-payments-beta -> r_sffx6l4z6mpqliki) EmDash Registry installation identities in the plugin runtime, route manifests, and callback/store-proof contract with dinkuskit.com.
  • Add the @running Payments setup journey (src/registry/setup-journey.ts and docs/payments-setup-journey.md) that opens Payment setup, connects with DinkusKit.com in Stripe test mode, clicks Check connection, and verifies Connected: Stripe test mode.
  • Rework .github/workflows/emdash-release.yml, .github/workflows/release.yml, .github/workflows/changeset-check.yml, .github/workflows/preview.yml, .github/scripts/*, scripts/release-flow.mjs, and RELEASING.md to match release-beta-cut-071 (manual beta cuts, beta-gated release PR promotion, dedicated release GitHub App authentication, OIDC + actions/attest-build-provenance + emdash-cms/emdash/apps/release-action delegated Registry publishing with PDS record checksum verification and no stored PDS credentials, < 131072-byte sandbox bundle check, and v0.2.8 baseline tag documentation).

• #56 8415c8c Thanks @saariuslystoned! - Keep connection diagnostics in the recovery-required state after a consumed country repair, matching connection status and preserving the recorded failure detail.

• #58 e523b48 Thanks @saariuslystoned! - Payment setup page: returning from DinkusKit's Approve finishes sign-in on its own and shows the real payment connection; Continue pressed early waits out DinkusKit's short poll interval instead of showing the same screen; a lapsed 5-minute page sign-in shows the last checked result with its time; a refused Stripe setup names its known reason instead of "not confirmed"; when Stripe needs more information the page points to Set up or resume Stripe, which lists what is missing.