Skip to content

fix: preserve lockfile graph during versioning#19

Merged
jan-kubica merged 1 commit into
mainfrom
fix/changeset-lock-safety
Jul 24, 2026
Merged

fix: preserve lockfile graph during versioning#19
jan-kubica merged 1 commit into
mainfrom
fix/changeset-lock-safety

Conversation

@jan-kubica

Copy link
Copy Markdown
Contributor

Summary

  • synchronize cached Bun workspace self-versions without regenerating the resolved dependency graph
  • make Changesets versioning use the synchronizer followed by a frozen install
  • gate CI with the same code in check-only mode
  • add executable invariants and generated repository guidance that prohibit lockfile deletion during versioning

Validation

  • real @stll/oxlint-config 0.4.0 → 0.4.1 → 0.4.0 round trip; both frozen installs passed and bun.lock returned byte-identical (SHA-256 eb37eb7bddb3c7075fc9ae90d5a8f08cb0f02ed4202ad64ee431308a93e52fcb)
  • bun run typecheck
  • bun run test
  • bun run lint
  • bun run publint
  • bun run pack:dry-run
  • bun run test:rust-lints

CC on behalf of @jan-kubica

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 5 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 20d778bf-857b-4ae0-be3a-85ccc0e6899a

📥 Commits

Reviewing files that changed from the base of the PR and between 93ddf6c and 76c80e1.

📒 Files selected for processing (7)
  • .ai/local/agents.md
  • .github/workflows/ci.yml
  • AGENTS.md
  • package.json
  • scripts/bun-lock-workspace-versions.test.ts
  • scripts/check-lockfile-workspace-versions.ts
  • scripts/lib/bun-lock-workspace-versions.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/changeset-lock-safety

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.

@jan-kubica
jan-kubica merged commit 0d6eb1a into main Jul 24, 2026
6 checks passed
@jan-kubica
jan-kubica deleted the fix/changeset-lock-safety branch July 24, 2026 12:54
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant