CI: Audit a freshly-resolved Cargo.lock in addition to pinned locks

The checked-in Cargo-minimal.lock and Cargo-recent.lock are only as
fresh as their last manual update, so advisories affecting versions
that the resolver would pick right now can slip through between lock
refreshes. Add a matrix leg that runs `cargo generate-lockfile` before
auditing, giving us clean-slate coverage on every scheduled run.

Co-Authored-By: HAL 9000
Signed-off-by: Elias Rohrer <dev@tnull.de>

Author: tnull

.github/workflows/audit.yml

@@ -18,10 +18,14 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        lockfile: [Cargo-minimal.lock, Cargo-recent.lock]
+        lockfile: [Cargo.lock, Cargo-minimal.lock, Cargo-recent.lock]
     steps:
       - uses: actions/checkout@v4
+      - name: Generate fresh Cargo.lock
+        if: ${{ matrix.lockfile == 'Cargo.lock' }}
+        run: cargo generate-lockfile
       - name: Use ${{ matrix.lockfile }}
+        if: ${{ matrix.lockfile != 'Cargo.lock' }}
         run: cp ${{ matrix.lockfile }} Cargo.lock
       - uses: rustsec/audit-check@v2.0.0
         with: