Skip to content

chore: bump managed zccache 1.12.8 -> 1.12.9, version 2.2.30 -> 2.2.31#662

Merged
zackees merged 1 commit into
mainfrom
chore/bump-managed-zccache-1.12.9
Jun 20, 2026
Merged

chore: bump managed zccache 1.12.8 -> 1.12.9, version 2.2.30 -> 2.2.31#662
zackees merged 1 commit into
mainfrom
chore/bump-managed-zccache-1.12.9

Conversation

@zackees

@zackees zackees commented Jun 20, 2026

Copy link
Copy Markdown
Member

Summary

Bumps fbuild's pinned zccache release to 1.12.9 (Windows daemon unstick fix from zccache#775 + the v2 IPC scaffolding from zccache#778–#781). Bumps fbuild's own version 2.2.30 -> 2.2.31 so the autonomous-release action ships a wheel that resolves the new managed download.

What ships

  • crates/fbuild-build/src/managed_zccache.rsMANAGED_ZCCACHE_VERSION and RELEASE_TAG 1.12.8 -> 1.12.9
  • crates/fbuild-daemon/src/models.rsDaemonInfoResponse test-fixture strings updated in lockstep
  • Cargo.toml, pyproject.toml, Cargo.lock — workspace + Python version 2.2.30 -> 2.2.31

Coordination

Coordinated with zackees/zccache#783 (already merged + published — 1.12.9 is live on PyPI + crates.io + GitHub Releases). fbuild's managed-zccache downloader will resolve the new tag immediately on next run.

Test plan

  • zccache 1.12.9 published on PyPI + crates.io + GitHub Releases before this PR opened (verified via gh run view 27854992359 --repo zackees/zccache → all green)
  • fbuild CI on this PR is green
  • After merge: release-auto.yml detects the version bump, builds wheels, ships fbuild 2.2.31 to PyPI

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Released version 2.2.31
    • Updated a build dependency to its latest patch version

Bumps fbuild's pinned zccache release to 1.12.9 (Windows daemon
unstick fix from zccache#775, plus v2 IPC scaffolding in zccache#778
through zccache#781 — v2 surface ships alongside v1, no behavior
change here).

Bumps fbuild's own workspace + Python package version to 2.2.31 so
the autonomous-release action ships a wheel that resolves the new
managed download.

- crates/fbuild-build/src/managed_zccache.rs: MANAGED_ZCCACHE_VERSION
  and RELEASE_TAG both move 1.12.8 -> 1.12.9.
- crates/fbuild-daemon/src/models.rs: DaemonInfoResponse test fixture
  strings updated in lockstep so the example install-status reflects
  the new pin.
- Cargo.toml, pyproject.toml, Cargo.lock: workspace + Python version
  2.2.30 -> 2.2.31.

Coordinated with zackees/zccache#783.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e5abcd5d-fc21-47dd-9546-2054738a1d3d

📥 Commits

Reviewing files that changed from the base of the PR and between ac187a5 and 284638b.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (4)
  • Cargo.toml
  • crates/fbuild-build/src/managed_zccache.rs
  • crates/fbuild-daemon/src/models.rs
  • pyproject.toml

📝 Walkthrough

Walkthrough

Bumps the workspace package version from 2.2.30 to 2.2.31 in both Cargo.toml and pyproject.toml. Updates the pinned managed zccache version constant from 1.12.8 to 1.12.9 in managed_zccache.rs, along with the matching release tag, and updates the corresponding test fixture lockfile name.

Changes

Version Bump and zccache Pin Update

Layer / File(s) Summary
zccache version pin and test fixture
crates/fbuild-build/src/managed_zccache.rs, crates/fbuild-daemon/src/models.rs
MANAGED_ZCCACHE_VERSION and RELEASE_TAG updated from 1.12.8 to 1.12.9; DaemonInfoResponse test fixture updated to use the new version string and lockfile name (.zccache-1.12.9.install.lock).
Package version bump to 2.2.31
Cargo.toml, pyproject.toml
[workspace.package] version and [project] version incremented from 2.2.30 to 2.2.31.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • FastLED/fbuild#535: Same release-chore pattern bumping Cargo.toml and pyproject.toml version fields in tandem.
  • FastLED/fbuild#575: Directly modifies the same MANAGED_ZCCACHE_VERSION and RELEASE_TAG constants in managed_zccache.rs.
  • FastLED/fbuild#579: Updates the same managed_zccache.rs version/tag constants to point the installer at a different pinned zccache release.

Poem

🐇 Hop, hop, a tiny version leap,
From .30 to .31 — oh what a feat!
The zccache bumped from eight to nine,
New lockfiles named, everything's fine.
A rabbit stamps the release with glee! 🎉

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: bumping managed zccache from 1.12.8 to 1.12.9 and fbuild version from 2.2.30 to 2.2.31, matching the primary objectives of the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-managed-zccache-1.12.9

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 and usage tips.

@zackees zackees merged commit e165ea4 into main Jun 20, 2026
85 of 91 checks passed
@fastled-project-sync fastled-project-sync Bot moved this to Triage in FastLED Tracker Jun 20, 2026
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