Skip to content

fix: drop unused either dependency in minimald - #1081

Merged
twitchyliquid64 merged 1 commit into
mainfrom
inbox-patch/drop-unused-either-ba9a7b91770b6820
Jul 29, 2026
Merged

fix: drop unused either dependency in minimald#1081
twitchyliquid64 merged 1 commit into
mainfrom
inbox-patch/drop-unused-either-ba9a7b91770b6820

Conversation

@gominimal-aw-bot

@gominimal-aw-bot gominimal-aw-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Fixes #1022
Routing-Key: inbox-route/I_kwDOSUhdos8AAAABKmXn2Q

cargo-machete flagged either as declared in crates/minimald/Cargo.toml with no use in the crate, failing the nightly-tests hygiene job. A search of crates/minimald confirms the crate never references the either crate — every either/Either match is the English word inside a comment — so the declaration is orphaned. Removed the either.workspace = true line and resynced Cargo.lock; either stays a transitive dependency, so only minimald's dependency entry changed (no version bumps). Matches prior minimald unused-dep cleanups (informed by #594, #448).

Verification

cargo fmt --all --check — pass, no drift
cargo clippy --workspace --locked -- -D warnings — pass, 0 warnings
cargo build --workspace --locked — pass, Finished dev profile
cargo test --workspace --locked — pass, all suites ok (0 failed)

Generated by inbox-patch ·

Note

Remove unused either dependency from minimald

Removes the either workspace dependency from crates/minimald/Cargo.toml and updates the lockfile accordingly.

Macroscope summarized 23fb694.

cargo-machete's hygiene check flagged `either` as declared in
crates/minimald/Cargo.toml with no use in the crate, turning the
nightly-tests hygiene job red. Searching crates/minimald confirms
the crate never references the either crate: every `either`/`Either`
occurrence is the English word inside a comment. Remove the orphaned
declaration, matching prior unused-dep cleanups in minimald (chrono
in #594, nix in #448).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

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

Run ID: 5c10204c-64f7-4fed-be45-f8ded02225b6

📥 Commits

Reviewing files that changed from the base of the PR and between 6fa4175 and 23fb694.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • crates/minimald/Cargo.toml

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

@norrietaylor
norrietaylor marked this pull request as ready for review July 29, 2026 20:58
@norrietaylor
norrietaylor enabled auto-merge (squash) July 29, 2026 20:58
@twitchyliquid64
twitchyliquid64 disabled auto-merge July 29, 2026 21:12
@twitchyliquid64
twitchyliquid64 merged commit b5cd768 into main Jul 29, 2026
27 checks passed
@twitchyliquid64
twitchyliquid64 deleted the inbox-patch/drop-unused-either-ba9a7b91770b6820 branch July 29, 2026 21:12
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.

cargo-machete: unused dependency either in minimald fails nightly hygiene

2 participants