fix(ci): verify Gitleaks release archives - #610
Merged
Lutar, Stephen P. (stephenlutar2-hash) merged 1 commit intoAug 13, 2026
Merged
fix(ci): verify Gitleaks release archives#610Lutar, Stephen P. (stephenlutar2-hash) merged 1 commit into
Lutar, Stephen P. (stephenlutar2-hash) merged 1 commit into
Conversation
Verify the official Gitleaks 8.21.2 Linux x64 archive before extraction. Use one pinned SHA-256 across GitHub Actions, CircleCI, and the portal workflow. Make the portal optional config argument-safe without changing scan coverage. Align current secret-scanning docs with the active security.yml workflow. Validation: - git diff --check - strict YAML parse for three CI configs - Actionlint and ShellCheck - Linux checksum, extraction, and exact-version probe - full project secret scan and 15 scanner tests - pnpm 10.26.1 typecheck (182/182 tasks) Workcell: SECRET-SCAN-INTEGRITY Signed-off-by: Lutar, Stephen P. <stephenlutar2@gmail.com>
Member
Author
|
Codex (@codex) review Exact-head release review requested for |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback". |
Lutar, Stephen P. (stephenlutar2-hash)
merged commit Aug 13, 2026
8745cf0
into
main
55 of 56 checks passed
Lutar, Stephen P. (stephenlutar2-hash)
deleted the
agent/harden-secret-scan-integrity-v3
branch
August 13, 2026 11:12
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
1 participant
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
security.ymlworkflow.Scope
Verification
git diff --checkCurrent-main lineage
This is the clean mapped-identity successor after #606 advanced
main.It is parented directly on
e0cb7c61744fb64c15f59464e61c7fde15755e3a.Its stable patch ID matches #607 and #609:
fa769b46dfcfcf6023513282607d1a1b910ecd69.#609 was rejected before merge because GitHub classified its local placeholder
committer identity as
no_user. No published history was rewritten.Evidence boundary
The nested portal workflow is not a root platform hosted workflow at its current path.
It is hardened as a tracked extraction/template surface.
Merge gate
Require a valid GitHub signature and DCO, terminal exact-head hosted checks,
resolved threads, and a normal protected squash merge.
Workcell:
SECRET-SCAN-INTEGRITYSupersedes: #609, #607
Follow-up to: #604