Upgrade Rust to 1.99.0 (LIM-1515)

Merged
RM
4d ago
+13-13

User description

Summary

Bumps the pinned Rust toolchain from 1.98.1 to 1.99.0 in lockstep.

Pin-site audit

  • Cargo.toml rust-version: 1.98.1 → 1.99.0
  • ci/ap-check/Cargo.toml rust-version: 1.98.1 → 1.99.0
  • .github/workflows/ci.yml: 2 sites (step names + toolchain:) → 1.99.0
  • scripts/verify.sh, AGENTS.md, docs/compile-cost.md: doc/comment references updated
  • No rust-toolchain.toml, Dockerfile, or devcontainer exists
  • CHANGELOG.md 0.1.0 entry left as-is (historical)

Package exclusions

Cargo.toml already uses an explicit include allow-list; cargo package --list --locked shows only sources, README, CHANGELOG, licenses and the two normative docs. No change needed.

Verification

cargo check --no-default-features --locked passes on local rustc 1.99.1 (newer than 1.99.0 pin; CI will exercise 1.99.0).


Generated by Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.


Summary by cubic

Bumps the pinned Rust toolchain from 1.98.1 to 1.99.0 across the repo.

  • Updates the MSRV in both Cargo.toml and ci/ap-check/Cargo.toml.
  • Updates the toolchain pins in .github/workflows/ci.yml and the version references in AGENTS.md, docs/compile-cost.md, and scripts/verify.sh.
  • No packaging changes needed; the existing include allow-list already covers all required files.

CodeAnt-AI Description

Require Rust 1.99.0 and validate builds with that toolchain

What Changed

  • The crate’s minimum supported Rust version is now 1.99.0 instead of 1.98.1
  • CI installs Rust 1.99.0 for build, test, and release checks
  • Build guidance now reflects the updated Rust version requirement

Impact

✅ Clear Rust version requirement for crate users
✅ CI checks builds against Rust 1.99.0

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.