Skip to content

ci: establish Minimum Supported Rust Version (MSRV) policy and test it in CI #14

Description

@rmems

Summary

Declare an MSRV (Minimum Supported Rust Version — the oldest Rust toolchain version we guarantee the crate will build + pass tests on) for engram-parser (e.g. the lowest stable that builds clean with current features), document it in Cargo.toml (rust-version) + README, and add explicit CI job/matrix entry testing on that toolchain (fmt/clippy/test --all-features) alongside stable. Follow common Rust lib practice and corinth patterns where relevant. (User note: IDK what is MSRV — definition added here.)

Motivation

Scope

  • Choose/verify MSRV (use cargo-msrv or manual; current edition="2024" implies recent, but pin e.g. 1.80+ or whatever works).
  • Add rust-version = "1.XX" to [package] in Cargo.toml.
  • Update ci.yml (or harden issue) to include a "msrv" job: dtolnay/rust-toolchain with toolchain: 1.XX , then cargo check/test etc.
  • README: "MSRV: 1.XX (tested in CI on stable + MSRV)".
  • Perhaps clippy on MSRV too (with allowances if needed).
  • Cross links.

Non-goals

  • Testing beta/nightly in main CI (optional separate).
  • MSRV bumps in same PR as features (separate).
  • Polyfill or compat shims.

Acceptance Criteria

Open Questions

Related


Standard for publishable Rust crates under Limen-Neural.

Drafted and planned with assistance from Grok Build (xAI) for Limen-Neural/engram-parser (2026-07-03). Cite as Grok Build when creating.

Activity

  1. self-assigned this
    on Jul 3, 2026
  2. added a commit that references this issue on Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions