Repository navigation
Add CI, cargo-deny and publish to crates.io on release - #3
Merged
Merged
Conversation
CI runs fmt, clippy, the all-features check and the tests on Linux, Windows and macOS, plus a ci-ok gate and a coverage report. Security runs cargo-deny weekly and on dependency changes. Release checks the tag against Cargo.toml, dry-runs the package and publishes with crates.io trusted publishing instead of a stored token. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Moves the authentication check and the request headers into their own helpers, bringing query below a cyclomatic complexity of 15 (was 18). Co-Authored-By: Claude Sonnet 5.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
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
ci-okgate job and a coverage report (master only).Cargo.lockis not versioned (library), so no--locked. No wasm32 job:jsonwebtokenandrandneed getrandom's browser backend there, which is a design decision for the crate, not a CI one.security.yml+deny.toml(cargo-deny, weekly and on dependency changes).RUSTSEC-2023-0071(rsaviajsonwebtoken) is ignored: only public-key verification happens here, and there is no fixed release.release.ymlchecks that the tag matches theCargo.tomlversion, dry-runs the package and publishes with crates.io trusted publishing, replacing the storedCARGO_TOKEN. Run by hand it only does the dry run.querysplit into two helpers; no function is above a cyclomatic complexity of 15 now (was 18).One-time setup (crates.io)
Crate Settings > Trusted Publishing > add: owner
rafaga, repositoryesi-openapi, workflowrelease.yml.Test plan
cargo test,cargo deny checkandcargo publish --dry-runpass locally.🤖 Generated with Claude Code