Skip to content

chore: version packages - #65

Merged
cavewebs merged 3 commits into
mainfrom
cursor/version-packages-core-034-68fa
Nov 5, 2026
Merged

cavewebs merged 3 commits into
mainfrom
cursor/version-packages-core-034-68fa

Conversation

@cavewebs

@cavewebs cavewebs commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Releases

@dashcommerce/core@0.3.4

Patch Changes

  • Republish with a fresh build so the shipped dist matches main (EmDash peer <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

  • Updated dependencies:
    • @dashcommerce/core@0.3.4

Why this bump

npm's published @dashcommerce/core@0.3.3 has the correct package.json peer (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.js has var version = "0.3.2"
  • dist/version-check still has SUPPORTED_EMDASH_PEER = ">=0.37.0 <0.38.0 || >=1.1.0 <1.4.0"

Source on main already has the <1.5.0 range 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.md so the hardcoded npm version line is 0.3.4 instead of the stale 0.2.2.

After merge: rebuild before publish

Do not publish from the existing dist/. After this lands on main:

  1. Rebuild: cd packages/core && bun run build
  2. Confirm local dist has 0.3.4 and the runtime peer range <1.5.0
  3. Publish 0.3.4 to npm next
  4. Inspect the tarball (npm pack or the published files): dist/index.js version is 0.3.4, version-check peer is <1.5.0
  5. Promote next to latest

Skip the rebuild and 0.3.4 will ship another stale dist, same as 0.3.3.

Open in Web Open in Cursor 

cursoragent and others added 3 commits November 5, 2026 07:45
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>
@cavewebs
cavewebs merged commit bd6e875 into main Nov 5, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants