chore: CI + Trusted Publishing (OIDC) + edition 2024 + MSRV + cargo-audit - #1
Merged
Merged
Conversation
…udit - Cargo.toml: edition 2021 -> 2024, add rust-version = "1.85" (MSRV) - .github/workflows/ci.yml: fmt --check, clippy -D warnings, test, release build on push/PR to main (repo previously had no CI) - .github/workflows/publish-crate.yml: crates.io Trusted Publishing via OIDC (rust-lang/crates-io-auth-action), tag/version guard, crates-io environment — no long-lived token - .github/workflows/audit.yml: cargo-audit on manifest changes + weekly - src/lib.rs: fix broken doctest — referenced nonexistent faf::FafDocument; now uses the real API (faf::parse / project_name / score). Pre-existing breakage; would have failed the new CI. - Cargo.lock: rand 0.9.2 -> 0.9.4, clears RUSTSEC-2026-0097 (unsound warning). Lockfile-only; manifest deps untouched (faf-rust-sdk stays at 1.3). Co-Authored-By: Claude Fable 5 <noreply@anthropic.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.
Changes
2021→2024, addedrust-version = "1.85"(MSRV). Manifest dependencies untouched (faf-rust-sdk = "1.3"pin left as-is)..github/workflows/ci.yml(new) —cargo fmt --check,cargo clippy -- -D warnings,cargo test,cargo build --releaseon push/PR tomain. Repo previously had no CI..github/workflows/publish-crate.yml(new) — crates.io Trusted Publishing via OIDC (rust-lang/crates-io-auth-action@v1), tag-vs-Cargo.toml version guard, runs in thecrates-ioenvironment. No long-livedCARGO_REGISTRY_TOKENsecret needed..github/workflows/audit.yml(new) —cargo auditon Cargo.toml/Cargo.lock changes + weekly schedule.faf::FafDocument; now uses the real re-exported API (faf::parse(...)→FafFile::project_name()/score()). Pre-existing breakage (unrelated to the edition bump) that would have failed the new CI'scargo test.rand 0.9.2→0.9.4, clears RUSTSEC-2026-0097 (unsound warning). Lockfile-only change.Verification (local, after changes)
cargo build— cleancargo build --release— cleancargo test— 1 doctest passing (meta-crate; no unit tests by design)cargo clippy --all-targets -- -D warnings— cleancargo fmt --check— cleancargo audit— clean (0 vulnerabilities, 0 warnings after rand update)Owner note
Before first publish: crates.io → faf → Settings → Trusted Publishing → add GitHub publisher (repository Wolfe-Jam/faf-crate, workflow publish-crate.yml, environment crates-io).
🤖 Generated with Claude Code