Skip to content

fix: build before publish + republish with dist (0.2.2)#21

Merged
SutuSebastian merged 2 commits into
mainfrom
fix/release-build-before-publish
Jul 18, 2026
Merged

fix: build before publish + republish with dist (0.2.2)#21
SutuSebastian merged 2 commits into
mainfrom
fix/release-build-before-publish

Conversation

@SutuSebastian

@SutuSebastian SutuSebastian commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Build + assert exports dist paths before pack in scripts/release.ts.
  • Patch changeset so Version PR ships 0.2.2 with dist/ (0.2.x omitted it).

Test plan

  • CI green
  • After Version PR merge: npm pack @stainless-code/layers@0.2.2 includes dist/index.mjs

0.2.0/0.2.1 tarballs shipped without dist because release packed a clean checkout. Build first, refuse pack when export targets are missing, and bump a patch republish.
@changeset-bot

changeset-bot Bot commented Jul 18, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7cdeb3e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages
Name Type
@stainless-code/layers Patch
@stainless-code/layers-devtools Patch
@stainless-code/react-layers-devtools Patch
@stainless-code/react-layers Patch
@stainless-code/vue-layers Patch
@stainless-code/solid-layers Patch
@stainless-code/svelte-layers Patch
@stainless-code/preact-layers Patch
@stainless-code/alpine-layers Patch
@stainless-code/lit-layers Patch
@stainless-code/angular-layers Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@SutuSebastian, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1ed900c3-ec1d-45cc-bcd1-cb698c2af289

📥 Commits

Reviewing files that changed from the base of the PR and between ea4cfa9 and 7cdeb3e.

📒 Files selected for processing (2)
  • .changeset/republish-dist.md
  • scripts/release.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-build-before-publish

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@SutuSebastian
SutuSebastian merged commit dc1d138 into main Jul 18, 2026
15 checks passed
@SutuSebastian
SutuSebastian deleted the fix/release-build-before-publish branch July 18, 2026 06:41
@github-actions github-actions Bot mentioned this pull request Jul 18, 2026
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.

1 participant