Conversation
#1417's stryker-mutation.yml referenced a hallucinated SHA for actions/upload-artifact (9eaf0eba... claimed v5.1.0) which doesn't resolve, causing every workflow run to fail at "Set up job". Replaced with the SHA already in use elsewhere in the repo (scorecard.yml uses 043fb46d... for v7.0.1). Per Otto-364 search-first-authority + the in-repo pattern check, this SHA is verified to resolve and is the version Zeta has standardized on. Surfaced empirically: #1420's CI run (databaseId 25283000236) failed with "Unable to resolve action actions/upload-artifact@9eaf0eba..." on the very first invocation of the new workflow. Author-time discipline (next time): when adding an action SHA, grep the repo first for an existing pin to that action — it's authoritative and tested. Don't make up SHAs. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Fixes a broken GitHub Actions workflow pin in the Stryker mutation-testing CI by replacing a non-resolving (hallucinated) commit SHA for actions/upload-artifact with a SHA already used elsewhere in the repo.
Changes:
- Update
.github/workflows/stryker-mutation.ymlto use the repo-standard pinned SHA foractions/upload-artifact(v7.0.1).
AceHack
added a commit
that referenced
this pull request
May 3, 2026
…1426-close shard (#1429) Substantial work since 1512Z: math-proofs C3 row went 0/15 -> ~12/15 (PN-Counter + OR-Set + LWW-Register + MerkleTree property tests); Stryker SHA hallucination caught empirically and fixed (#1421); B-0087 option-A landed (#1427) closing the workflow-startup-failure half; #1426 closed honestly after 5 reviewer-surfaced distinct correctness issues with B-0185 redesign-row filed. Discipline lesson: diminishing-returns recognition as first-class. When reviewer feedback surfaces valid distinct issues each iteration (not the same one redux), close + redesign-row + pivot to higher- leverage friction-reducing work. Composes with action hierarchy. Memory landed: feedback_action_sha_hallucination_check_repo_first_aaron_2026_05_03.md Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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
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
#1417's
.github/workflows/stryker-mutation.ymlreferenced a hallucinated SHA foractions/upload-artifact(9eaf0eba75d52b5e72c7a193fc2887e6caf95df0claimed v5.1.0) which doesn't resolve. Every workflow run fails at the "Set up job" step withUnable to resolve action.Fix
Replaced with the SHA already pinned elsewhere in the repo (
scorecard.ymluses043fb46d1a93c77aae656e7c1c64a875d1fc6a0afor v7.0.1). Per Otto-364 search-first-authority + the in-repo-pattern audit, this SHA is verified to resolve and is the version Zeta has standardized on.Empirical surface
#1420's CI run (
databaseId 25283000236) failed withUnable to resolve action actions/upload-artifact@9eaf0eba...on the very first invocation of the new workflow.Author-time discipline (next time)
When adding an action SHA, grep the repo first for an existing pin to that action — it's authoritative and tested. Don't make up SHAs from imagined version numbers.
Test plan
🤖 Generated with Claude Code