Repository navigation
EmDash 1.x peer catch-up - #36
Merged
Merged
Conversation
Widen @dashcommerce/core's emdash peer to 0.37.x or 1.1+, keep the runtime check honest, and ship a 1.1.0 patch for webhook body cloning and raw Response passthrough. Starter tracks 1.1; CI still matrixes 0.37 for the published plugin. Co-authored-by: Timchosen Uzua <timchosen@gmail.com>
cavewebs
marked this pull request as ready for review
October 6, 2026 11:58
Merged
cavewebs
added a commit
that referenced
this pull request
Oct 6, 2026
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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.2.2 ### Patch Changes - [#36](#36) [`2b462ee`](2b462ee) Thanks [@cavewebs](https://github.com/cavewebs)! - Widen the `emdash` peer to `>=0.37.0 <0.38.0 || >=1.1.0 <2.0.0` so current EmDash 1.x installs pass peer checks without bricking 0.37.x. The runtime compatibility check matches that range (skipping untested 0.38–0.42 and the mistaken `emdash@1.0.0` publish). Dual-version patches keep Stripe webhook raw-body reads and raw `Response` passthrough working on both 0.37.0 and 1.1.0. ## @dashcommerce/starter@0.3.3 ### Patch Changes - Updated dependencies [[`2b462ee`](2b462ee)]: - @dashcommerce/core@0.2.2
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
2 participants
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.
I widened
@dashcommerce/core's emdash peer so current 1.x installs work, without bricking 0.37.x.Peer:
>=0.37.0 <0.38.0 || >=1.1.0 <2.0.0. The runtime compatibility check matches that range (0.38–0.42 and the mistakenemdash@1.0.0publish stay out). DevDeps and the starter track 1.1.0. CI still matrixes 0.37.0 against core; the starter stays on 1.x migrations/emdash/internal/*.1.x needed a new patch — plugin dispatch moved to
http-route-dispatch, andparseRouteInputstill consumes the body. Officialresponse: "raw"is not a substitute; it stripsSet-Cookie.Supersedes #28 (that branch only widened to
<0.39).