chore: version packages#17
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@dashcommerce/core@0.1.5
Patch Changes
#16
b865dd7Thanks @cavewebs! - Support EmDash 0.28.Migrate from emdash 0.6 to 0.28.1. The plugin now builds its native
ResolvedPluginviadefinePluginwith single-argumentRouteContexthandlers (emdash's native route shape) instead of
adaptSandboxEntry, whose0.28 form flattens the request and would break the Stripe webhook's raw-body
signature check. Capability names are updated to the current vocabulary
(
network:request,content:read,content:write,media:read,users:read), and the emdash peer range is now>=0.28.0 <0.29.0.The bundled emdash patch is re-authored for 0.28.1: plugin route handlers may
still return a raw
Response(cookies, redirects, webhook 200s), and the rawrequest body is preserved so
ctx.request.text()works for Stripe webhooksignature verification.
The starter adds a Cloudflare Worker entry (
src/worker.ts) plus a CronTrigger so plugin cron — abandoned-cart recovery, subscription dunning, and
stock-lock sweeps — runs on Workers (emdash 0.19+ drives cron from a
scheduled()handler, not request side effects).@dashcommerce/starter@0.3.1
Patch Changes
#16
b865dd7Thanks @cavewebs! - Support EmDash 0.28.Migrate from emdash 0.6 to 0.28.1. The plugin now builds its native
ResolvedPluginviadefinePluginwith single-argumentRouteContexthandlers (emdash's native route shape) instead of
adaptSandboxEntry, whose0.28 form flattens the request and would break the Stripe webhook's raw-body
signature check. Capability names are updated to the current vocabulary
(
network:request,content:read,content:write,media:read,users:read), and the emdash peer range is now>=0.28.0 <0.29.0.The bundled emdash patch is re-authored for 0.28.1: plugin route handlers may
still return a raw
Response(cookies, redirects, webhook 200s), and the rawrequest body is preserved so
ctx.request.text()works for Stripe webhooksignature verification.
The starter adds a Cloudflare Worker entry (
src/worker.ts) plus a CronTrigger so plugin cron — abandoned-cart recovery, subscription dunning, and
stock-lock sweeps — runs on Workers (emdash 0.19+ drives cron from a
scheduled()handler, not request side effects).Updated dependencies [
b865dd7]: