Conversation
Run security audits against all three checked-in lock files using the official rustsec/audit-check action. Triggers on push, PRs, and daily via cron to catch newly published advisories. Co-Authored-By: HAL 9000 Signed-off-by: Elias Rohrer <dev@tnull.de>
Addresses RUSTSEC-2026-0007 (bytes), RUSTSEC-2026-0067/0068 (tar), and RUSTSEC-2026-0097 (rand). Co-Authored-By: HAL 9000
|
cc @satsfy |
| strategy: | ||
| fail-fast: false | ||
| matrix: | ||
| lockfile: [Cargo.lock, Cargo-minimal.lock, Cargo-recent.lock] |
There was a problem hiding this comment.
Why is Cargo.lock part of the matrix?
There was a problem hiding this comment.
against all three checked-in lock files
Yeah there should only be two. Did I commit one in electrsd accidentally or something?
|
As it stands no-one is ever going to look at the auction run (well I definitely won't remember to do it). Can we have the action raise an issue if there are warnings? Or is that going to be too noisy? I don't have a lot of experience with |
|
The GitHub bot will usually open an issue when there is a new RUSTSEC (see bitcoindevkit/bdk#2178). |
|
Does that bot hit projects to use |
|
Actually, I think we need to use the This is name: Audit
on:
push:
paths:
# Run if workflow changes
- '.github/workflows/audit.yml'
# Run on changed dependencies
- '**/Cargo.toml'
- '**/Cargo.lock'
# Run if the configuration file changes
- '**/audit.toml'
# Rerun periodically to pick up new advisories
schedule:
- cron: '0 0 * * *' # Nightly
# Run manually
workflow_dispatch:
jobs:
audit:
runs-on: ubuntu-latest
permissions:
contents: read
issues: write
steps:
- uses: actions/checkout@v6
with:
persist-credentials: false
- uses: actions-rust-lang/audit@v1
name: Audit Rust DependenciesI could be talking out of my ass, I'm not certain about this. |
|
Sounds legit :) |
Run security audits against all three checked-in lock files using the official rustsec/audit-check action. Triggers on push, PRs, and daily via cron to catch newly published advisories.
Co-Authored-By: HAL 9000