Skip to content

chore(release): sync pyproject.toml to 2.3.16 to unblock release-auto#924

Merged
zackees merged 1 commit into
mainfrom
chore/release-2.3.16-lockstep-pyproject
Jul 1, 2026
Merged

chore(release): sync pyproject.toml to 2.3.16 to unblock release-auto#924
zackees merged 1 commit into
mainfrom
chore/release-2.3.16-lockstep-pyproject

Conversation

@zackees

@zackees zackees commented Jul 1, 2026

Copy link
Copy Markdown
Member

Cargo.toml was bumped to 2.3.16 (in c99579e) but pyproject.toml stayed at 2.3.15, causing every release-auto run since (ecd80c7, dbc2245) to fail in the Prepare-release step's Cargo/pyproject lockstep check.

Downstream: FastLED's fbuild==2.3.15 pin picks up 2.3.16 on the next uv sync, which includes the FastLED-org-transfer ACLPC_CHECKSUM fix from #915 (d08622b). That unblocks FastLED's LPC804/lpc845/lpcxpresso804/lpcxpresso845max build lanes.

Generated with Claude Code

Cargo.toml was bumped to 2.3.16 in c99579e but pyproject.toml stayed at
2.3.15, causing every release-auto run since (ecd80c7, dbc2245) to
fail in the 'Prepare release' step's Cargo/pyproject lockstep check.

Bump pyproject.toml so the release fires. Downstream: FastLED's
'fbuild==2.3.15' pin will pick up 2.3.16 on the next 'uv sync',
which includes the FastLED-org-transfer ACLPC_CHECKSUM fix from #915
(d08622b). That unblocks the LPC804/LPC845/lpcxpresso804/lpcxpresso845max
build lanes on FastLED, which have been red with 'sha256 mismatch
for FastLED-framework-arduino-lpc8xx/.../50d76e0d63c...tar.gz'
since GitHub's post-transfer tarball rebuild changed the archive
bytes for the same source commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@zackees
zackees merged commit 932b6e7 into main Jul 1, 2026
@zackees
zackees deleted the chore/release-2.3.16-lockstep-pyproject branch July 1, 2026 20:44
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 1 minute

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d66dffaf-c183-44c4-be9d-807b09349543

📥 Commits

Reviewing files that changed from the base of the PR and between 8a45859 and 1eb54d2.

📒 Files selected for processing (1)
  • pyproject.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-2.3.16-lockstep-pyproject

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

1 participant