Repository navigation
chore: version packages - #61
Merged
Merged
Conversation
cavewebs
added a commit
that referenced
this pull request
Nov 2, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> Sync failed on main after Version Packages merge #61: the "Regenerate standalone lockfile" step ran `bun install` with `@dashcommerce/core` pinned to `^0.3.3` before that version was on npm (publish is local OTP, after the merge). Failed run: https://github.com/emdashCommerce/dashcommerce/actions/runs/41427275420 ``` error: No version matching "^0.3.3" found for specifier "@dashcommerce/core" (but package exists) error: @dashcommerce/core@^0.3.3 failed to resolve ``` This retries `bun install` only for that unpublished-core error, for about five minutes with backoff (15s, 30s, 45s, then 60s). Other install failures still fail the job on the first attempt. Retries pass `--force` so bun does not reuse a 5-minute-stale registry manifest from the first miss. After eight attempts the step errors with a note to publish, then re-run the workflow. Please merge with a merge commit, not a squash. CI on this PR is typecheck/build/test. Sync itself only runs on push to main (or workflow_dispatch). Merging this re-runs Sync, which should catch the starter up now that 0.3.3 is on npm. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-f38d9137-2dfb-5846-986b-d9dffab211cf?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-f38d9137-2dfb-5846-986b-d9dffab211cf&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div>
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 publish to npm yourself or setup this action to publish 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.3.3
Patch Changes
37b9afcThanks @cavewebs! - Support EmDash 1.4.0. Shippatches/emdash@1.4.0.patch(same raw Response passthrough and request body clone fix as 1.3.1, retargeted at 1.4.0's hashed dist files). Widen the EmDash peer range to>=0.37.0 <0.38.0 || >=1.1.0 <1.5.0so create-emdash 1.4 installs pass peer checks. Cap below 1.5 so the next untested EmDash minor is still rejected.@dashcommerce/starter@0.3.8
Patch Changes
37b9afc]: