Skip to content

chore: upgrade - #2255

Merged
shunkakinoki merged 1 commit into
mainfrom
chore/upgrade
Aug 5, 2026
Merged

chore: upgrade#2255
shunkakinoki merged 1 commit into
mainfrom
chore/upgrade

Conversation

@shunkakinoki

@shunkakinoki shunkakinoki commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Automated upgrade

@indent-zero

indent-zero Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor
PR Summary

Rebased onto the latest main, which had independently absorbed the earlier Makefile reset hardening (#2252) and other work. The PR's effective delta vs. main is now just the moshi-hook overlay version bump, letting consumers pick up the newer upstream release on the next rebuild.

  • overlays/default.nix: bump moshi-hook version from 0.2.700.2.73 and refresh all four per-platform sha256 hashes (Linux x86_64, Linux aarch64, Darwin aarch64, Darwin x86_64) — all four verified against https://cdn.getmoshi.app/hook/v0.2.73/….

Issues

No issues found.

CI Checks

Waiting for CI checks...

@shunkakinoki
shunkakinoki enabled auto-merge (squash) August 5, 2026 01:54
@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

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

Next review available in: 35 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: 7f72640f-a254-4788-9615-41f2a7186e9d

📥 Commits

Reviewing files that changed from the base of the PR and between b99573f and 2ec5fb8.

📒 Files selected for processing (1)
  • overlays/default.nix
📝 Walkthrough

Summary by CodeRabbit

  • Updates
    • Updated the bundled Moshi Hook component to version 0.2.73.
    • Refreshed platform-specific packages to ensure compatibility with the new version.

Walkthrough

The moshi-hook derivation in overlays/default.nix updates from version 0.2.70 to 0.2.73. Source hashes change for four platform targets.

Changes

moshi-hook update

Layer / File(s) Summary
Update release and platform hashes
overlays/default.nix
The derivation now fetches moshi-hook version 0.2.73 with updated hashes for Linux x86_64, Linux AArch64, Darwin AArch64, and the fallback source.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Poem

A rabbit checks the hashes twice,
Then hops to release 0.2.73.
Four platforms shine with new supplies,
The derivation builds with ease,
And carrots mark the upgrade.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title indicates an upgrade but does not identify the upgraded package or version change. Specify the package and version change, such as "chore: upgrade moshi-hook to 0.2.73".
Description check ❓ Inconclusive The description indicates an automated upgrade but does not describe the specific package or version change. Mention that the change upgrades moshi-hook from 0.2.70 to 0.2.73 and updates its source hashes.
✅ Passed checks (3 passed)
Check name Status Explanation
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/upgrade

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.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

@shunkakinoki
shunkakinoki force-pushed the chore/upgrade branch 6 times, most recently from 7e91784 to 0272d5d Compare August 5, 2026 05:17
@shunkakinoki
shunkakinoki disabled auto-merge August 5, 2026 05:43
@shunkakinoki
shunkakinoki merged commit c198a98 into main Aug 5, 2026
4 of 6 checks passed
@shunkakinoki
shunkakinoki deleted the chore/upgrade branch August 5, 2026 05:43
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