Repository navigation
chore: version packages - #37
Merged
Merged
Conversation
cavewebs
added a commit
that referenced
this pull request
Oct 7, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Why After Version Packages [#37](#37) (`@dashcommerce/core@0.2.2`), **CI is green** on `main` but **Release is red**. npm is shipped locally (`npm publish --access public` from `packages/core`); Actions is not a working publisher. Verified on [Release run 37460919491](https://github.com/emdashCommerce/dashcommerce/actions/runs/37460919491) (and the same pattern on [#27](https://github.com/emdashCommerce/dashcommerce/actions/runs/37335940811)): 1. No pending changesets after the version PR merge. 2. `changesets/action` logs `No changesets found. Attempting to publish any unpublished packages to npm`. 3. It writes `.npmrc` from `NPM_TOKEN` and runs `bun run release` → `changeset publish`. 4. npm returns `E404 Not Found - PUT https://registry.npmjs.org/@dashcommerce%2fcore` — the usual failure when the token cannot publish the scope. The secret is **present but unusable**, not missing (so an `if: secrets.NPM_TOKEN != ''` skip would still run and fail). Pushes that only open/update a Version Packages PR stay green. Merging that PR is what turns `main` red. ## Change Small, reversible cut of the broken Actions publish path: - Keep `Release` on `push` to `main`. - Keep `changesets/action` **without** `publish:`, so it still opens/updates Version Packages PRs and exits 0 when there is nothing to version. - Drop `NPM_TOKEN`, `NPM_CONFIG_PROVENANCE`, `id-token: write`, `registry-url`, and `createGithubReleases` (all publish-only). - Document local publish in `.changeset/README.md`. `bun run release` in root `package.json` is unchanged for anyone who wants to publish from a logged-in machine. ## Not in this PR - No `NPM_TOKEN` refresh/rotation. - No changes to Sync starter token handling. - Does not claim Actions published anything. ## Reverse Restore `publish: bun run release`, `NPM_TOKEN`, and provenance on the `changesets/action` step if Actions npm auth is ever wired up for real. ## After merge The next `main` push runs Release without `changeset publish`, so the default branch check should go green. Version Packages PRs keep working the same way; npm still ships locally. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-e4a0b3cc-04c9-5fa5-95c0-4896db1713d4?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-e4a0b3cc-04c9-5fa5-95c0-4896db1713d4&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>
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"><source](https://cursor.com/assets/images/open-in-cursor-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-cursor-light.png"><img](https://cursor.com/assets/images/open-in-cursor-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div](https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div){kind=link}
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
1 participant
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.2.2
Patch Changes
2b462eeThanks @cavewebs! - Widen theemdashpeer to>=0.37.0 <0.38.0 || >=1.1.0 <2.0.0so 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 mistakenemdash@1.0.0publish). Dual-version patches keep Stripe webhook raw-body reads and rawResponsepassthrough working on both 0.37.0 and 1.1.0.@dashcommerce/starter@0.3.3
Patch Changes
2b462ee]: