[hyperpolymath]

Cargo ignores build metadata in a version requirement and warns on every build:

warning: version requirement 1.1.2+spec-1.1.0for dependencytoml includes semver metadata which will be ignored

Removed from rhodibot, cipherbot, finishingbot, glambot, panicbot (one-line edit) and seambot: toml = "1.1.2+spec-1.1.0" -> "1.1.2", serde_yaml = "0.9.34+deprecated" -> "0.9.34". No other occurrences in the tree.

Verification (per crate: rhodibot, cipherbot, finishingbot, glambot, panicbot, seambot)

• cargo build --locked: succeeds; Cargo.lock is untouched (git status shows only the six Cargo.toml files).
• cargo test --locked: all suites pass in all six crates.
• The warning is present on main and absent after (checked on rhodibot).

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Updated package version specifications across several components. These maintenance changes do not alter end-user functionality or introduce visible changes to the product.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Six bot manifests remove version metadata suffixes from toml requirements. The finishingbot and glambot manifests also remove a suffix from serde_yaml. The base version numbers remain unchanged.

Changes: Bot dependency specifications

Layer / File(s)	Summary
Update dependency version requirements bots/cipherbot/Cargo.toml, bots/finishingbot/Cargo.toml, bots/glambot/Cargo.toml, bots/panicbot/Cargo.toml, bots/rhodibot/Cargo.toml, bots/seambot/Cargo.toml	The manifests remove +spec-1.1.0 from toml requirements. The finishingbot and glambot manifests also remove +deprecated from serde_yaml requirements.

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

Change: Other

Merge Risk: Minimal · up to e262c

This change removes a Cargo warning about ignored build metadata in dependency requirements. It does not change which dependency versions are resolved, so there is no expected runtime or build impact.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chatgpt-codex-connector]

This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins.

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-13T11:05:04.736503Z	e262cb1	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.