Repository navigation
Record fleet scanner canary and audit lock regeneration #656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
10ef1f8
4c4ae83
3030f16
e238b41
f6d39e9
c1ef924
63ad3ad
9e27c07
d1b00d1
90c27f1
c0ab034
982c4c7
a42bfe2
03f2461
f0249dd
815bfa5
511e439
adb3028
f597f2a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| # SPDX-License-Identifier: MPL-2.0 | ||
| # PyPI wheel SHA-256 digests for CPython 3.12–3.14 on the Ubuntu x86_64 runner. | ||
| PyYAML==6.0.3 \ | ||
| --hash=sha256:ba1cc08a7ccde2d2ec775841541641e4548226580ab850948cbfda66a1befcdc \ | ||
| --hash=sha256:0f29edc409a6392443abf94b9cf89ce99889a1dd5376d94316ae5145dfedd5d6 \ | ||
| --hash=sha256:c458b6d084f9b935061bc36216e8a69a7e293a2f1e68bf956dcd9e6cbcd143f5 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -36,9 +36,9 @@ jobs: | |
| # authority, granting less rejects the run at startup with zero jobs. | ||
| permissions: | ||
| contents: read | ||
| uses: hyperpolymath/cicd-suite/.github/workflows/secret-scanner-reusable.yml@4404c3c0474e17753fe7689f3485c02890aac113 | ||
| uses: hyperpolymath/proven-cicd/.github/workflows/secret-scanner-reusable.yml@03e858b6015e67cc1f9bc31ac1e29ddc1b6fd409 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
For every PR or main push that scans this tree, the newly pinned callee is already known to fail its Rust supplement on four vendored Echidnabot lines containing environment-variable names and test credentials; Useful? React with 👍 / 👎. |
||
| with: | ||
| # The canary passed, but introduced-commit PR coverage is not approved. | ||
| # Every run continues to scan full history. | ||
| # The old-pin canary does not attest this new pin. Introduced-commit | ||
| # PR coverage is not approved; every run still scans full history. | ||
| fast-pr: false | ||
| # Deliberately no `secrets:` line — see the boundary note above. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
gh actions-lockchanges a workflow as well asactions.lock, this command only prints the diff and still lets the job continue with the mutated caller tree. That is already a real case here:docs/migrations/secret-scanner-cicd-suite/2026-11-09-repair-notes.mdsays a full v0.4.1 regeneration rewrites unrelated immutable action SHAs to tags. The following comparator starts from the regenerated roots and permits new roots, so removed SHA roots are not required to survive; the source audit likewise inspects the mutated worktree. The regeneration gate can therefore pass without proving that the regenerated lock represents the reviewed workflows, so it should fail on workflow changes other than the lockfile.Useful? React with 👍 / 👎.