build: track stable toolchain + declare MSRV 1.83; bump mailparse to 0.16.1#82
Merged
Merged
Conversation
….16.1 Set the rust-toolchain file to `stable` so dev/CI build against current stable, and declare the minimum supported Rust version explicitly via `rust-version = "1.83"` in Cargo.toml (the floor PyO3 0.29 requires). The CI lint/test/benchmark jobs now resolve their toolchain to stable (SHA pins on dtolnay/rust-toolchain unchanged); stale comments that referenced the old pinned 1.83 are updated. Upgrade mailparse 0.15.0 -> 0.16.1 (latest maintained release). The 0.16.x line is API-compatible (parse_mail, header get_key/get_value, get_body/get_body_raw, ctype.params/ctype.mimetype, subparts unchanged); the only changes are bug fixes (CRLF-before-boundary handling, no panic on multipart without a starting boundary). Full test suite (87 tests) passes identically on stable with no behavior change. Closes #37 Closes #38 Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolves two high-priority dependency/toolchain issues. Scope is limited to
Cargo.toml,Cargo.lock,rust-toolchain, and.github/workflows/test.yml— nosrc/,tests/, orpyproject.tomlchanges.#37 — Track stable toolchain, declare MSRV
rust-toolchain:1.83→stable, so dev/CI build against current stable.Cargo.toml: addedrust-version = "1.83"to[package]to declare the MSRV explicitly (the floor PyO3 0.29 requires).test.yml: thelint,test, andbenchmarkjobs now resolve their toolchain tostable(thedtolnay/rust-toolchainSHA pins are unchanged — only thetoolchain:value moved off1.83).security-auditalready used stable. Updated the stale comment that referenced "the repo's pinned 1.83".#38 — Audit & upgrade mailparse
0.16.1(2025-02-27). Upgradedmailparse 0.15.0→0.16.1and regeneratedCargo.lock.0.16.xline is API-compatible with the code insrc/mail_parser.rs—parse_mail, headerget_key/get_value,get_body/get_body_raw,ctype.params/ctype.mimetype, andsubpartsare all unchanged. The only changes betweenv0.15.0andv0.16.1are bug fixes: CRLF-before-boundary handling and not panicking on a multipart message with no starting boundary. Nosrc/changes were required.Verification
cargo buildsucceeds on stable.pytest --ignore tests/benchmark tests): 87 passed — identical to before the bump, no behavior change.Closes #37
Closes #38