Repository navigation
fix(ci): re-pin standards reusables and repair actions.lock #439
+121
−20
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| # SPDX-License-Identifier: MPL-2.0 | ||
| # cargo-audit configuration (read by `cargo audit` from .cargo/audit.toml). | ||
|
|
||
| [advisories] | ||
| # zip 8.6.0 extraction advisories. zip is reached only as a *build* | ||
| # dependency of utoipa-swagger-ui (src/interfaces/rest), whose build script | ||
| # unpacks the pinned Swagger UI archive; no echidna binary links zip or | ||
| # extracts untrusted archives at runtime. Every utoipa-swagger-ui release up | ||
| # to 10.0.1 requires zip ^8.6, so the >=9.0.0 fix cannot be selected yet. | ||
| # Remove these entries once utoipa-swagger-ui accepts zip >=9. | ||
| ignore = [ | ||
| "RUSTSEC-2026-0367", # SUID/SGID bits preserved during extraction | ||
| "RUSTSEC-2026-0368", # extract() symlinks pointing outside destination | ||
| "RUSTSEC-2026-0369", # extract() applies permissions through symlinks | ||
| ] |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,4 +18,4 @@ permissions: | |
|
|
||
| jobs: | ||
| governance: | ||
| uses: hyperpolymath/standards/.github/workflows/governance-reusable.yml@75bd5994470661a099df562d6d5ad2fe744dbd66 # main 2026-08-04 (lockfile-bearing ref: actions.lock required by caller-side enforcement, standards#570) | ||
|
There was a problem hiding this comment.
When this repository's Governance workflow runs, the new reusable always executes the JS-runtimes provisioning job, checks standards out beneath this repository, and runs Useful? React with 👍 / 👎.
Owner
Author
There was a problem hiding this comment. Right: that is hyperpolymath/standards#1296, which I opened for exactly this. The pin can only move once #1296 merges, because the reusable has to be pinned to a commit on standards. I'll move it in this PR then. The other jobs in the governance run are unaffected. Generated by Claude Code |
||
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Checked
generator-generic-ossf-slsa3-publish.ymlandsecurity-scan.yml: this patch adds theirslsa-framework/slsa-github-generator@f7dd8c54…andhyperpolymath/panic-attack@b689a74d…pins toworkflows, but neither key has a corresponding entry independencies. With Require lockfile enabled, every dependency of an onboarded workflow must be present, so these release-provenance and security-scan workflows remain startup-blocked andgh actions-lock --verify-localshould report incomplete coverage. Add the fully resolved records, or leave these workflows out of the lockfile until they can be resolved; see GitHub's workflow dependency lockfile requirements.Useful? React with 👍 / 👎.
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.
Agreed, and this is already called out in the PR body. Both refs were already dangling on main; the lock just didn't list them under their workflows. Their records need the numeric owner and repo IDs and the nested refs' commits. Only the GitHub API serves those, and this session has git-only access to both repositories. I won't write records I can't resolve.
Closing them is a mechanical follow-up for anyone with an authenticated
gh:close-lock.sh, thenprune-stale.sh. Until then those two workflows stay blocked at startup, as they already are on main. Leaving this thread open until that's done.Generated by Claude Code