Skip to content

chore: upgrade to edition 2024 and resolver 3#80

Draft
munendrasn wants to merge 9 commits into
salesforce-misc:mainfrom
munendrasn:chore/edition-2024
Draft

chore: upgrade to edition 2024 and resolver 3#80
munendrasn wants to merge 9 commits into
salesforce-misc:mainfrom
munendrasn:chore/edition-2024

Conversation

@munendrasn
Copy link
Copy Markdown
Collaborator

Summary

  • Upgrade Rust edition from 2021 to 2024 at workspace level, inherited by both crates
  • Upgrade resolver from 2 to 3 (MSRV-aware dependency resolution)
  • Fix edition 2024 compile errors:
    • Rename gengeneration (gen is a reserved keyword in 2024)
    • Remove explicit ref in pattern matches (disallowed when implicitly borrowing)

Why

  • Edition 2024 (stable since 1.85) brings stricter safety defaults, compatible with MSRV 1.88.0
  • Resolver 3 (stable since 1.84) considers rust-version when selecting dependency versions, preventing silent MSRV breakage on cargo update

Notes

Test plan

  • cargo check --workspace passes
  • cargo test --workspace passes
  • CI passes after rebase on main

munendrasn and others added 6 commits April 24, 2026 15:58
Add rust-toolchain.toml at the workspace root to pin the exact Rust
version and required components (clippy, rustfmt). This gives local
dev and CI a single source of truth — rustup reads the file
automatically, so developers no longer need to manually select a
version.

CI switches from the dtolnay/rust-toolchain action to `rustup show`,
which installs the pinned toolchain and components on the fly from
the checked-in file.

DEVELOPER.md updated to reference the toolchain file instead of a
hardcoded minimum version.
Edition 2024 (stable since 1.85) aligns with our MSRV 1.88.0 and
brings stricter safety defaults — `gen` is now a reserved keyword
and implicit borrowing disallows explicit `ref` in patterns.

Resolver 3 (stable since 1.84) is MSRV-aware: cargo will avoid
pulling dependency versions that require a newer Rust than the
workspace rust-version, preventing silent MSRV breakage on update.

Code fixes:
- Rename `gen` → `generation` in cache.rs and read_path.rs
- Remove explicit `ref` in pattern matches in read_path.rs
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