Repository navigation
chore: version packages - #65
Merged
Merged
Conversation
npm 0.3.3 shipped a stale 0.3.2 dist, so the runtime EmDash peer check still caps at <1.4.0. A patch bump lets us rebuild and publish a matching dist. See #63. Co-authored-by: Timchosen Uzua <timchosen@gmail.com>
Bump @dashcommerce/core to 0.3.4 so a fresh dist can be published after npm 0.3.3 shipped the 0.3.2 build. Starter follows to 0.3.9. See #63. Co-authored-by: Timchosen Uzua <timchosen@gmail.com>
Co-authored-by: Timchosen Uzua <timchosen@gmail.com>
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.
Releases
@dashcommerce/core@0.3.4
Patch Changes
<1.5.0/ runtime version-check). npm 0.3.3 incorrectly shipped the 0.3.2 dist. See #63.@dashcommerce/starter@0.3.9
Patch Changes
@dashcommerce/core@0.3.4Why this bump
npm's published
@dashcommerce/core@0.3.3has the correctpackage.jsonpeer (emdash>=0.37.0 <0.38.0 || >=1.1.0 <1.5.0) but the shipped dist is still the 0.3.2 build:dist/index.jshasvar version = "0.3.2"dist/version-checkstill hasSUPPORTED_EMDASH_PEER = ">=0.37.0 <0.38.0 || >=1.1.0 <1.4.0"Source on
mainalready has the<1.5.0range from #60. The 0.3.3 publish packed a stale dist. This PR only bumps versions so 0.3.4 can be rebuilt and published.Also updates
packages/core/README.mdso the hardcoded npm version line is0.3.4instead of the stale0.2.2.After merge: rebuild before publish
Do not publish from the existing
dist/. After this lands onmain:cd packages/core && bun run build0.3.4and the runtime peer range<1.5.0nextnpm packor the published files):dist/index.jsversion is0.3.4, version-check peer is<1.5.0nexttolatestSkip the rebuild and 0.3.4 will ship another stale dist, same as 0.3.3.