Skip to content

ci: fix workflow breakages across 4 workflows - #1

Closed
Masked18 wants to merge 1 commit into
mainfrom
fix/workflow-audit
Closed

ci: fix workflow breakages across 4 workflows#1
Masked18 wants to merge 1 commit into
mainfrom
fix/workflow-audit

Conversation

@Masked18

Copy link
Copy Markdown
Owner

What

Fixes bugs found during a full audit of all 16 CI workflows.

Changes

benchmarks.yml

  • Remove duplicate Enforce benchmark thresholds step (caused the job to always fail on YAML parse)
  • Fix Update baseline artifact path — referenced new.txt which is never produced; corrected to handlers_new.txt + subscriptions_new.txt
  • Upgrade security job from actions/checkout@v3 + setup-go@v4 to @v4 / @v5

fuzz.yml

  • Remove 3 dangling job references (fuzz-swap-exact-in, fuzz-swap-exact-out, fuzz-swap-raw-body) from the fuzz-summary needs array — those jobs don't exist so the summary always errored

test-jwt-hardening.yml

  • Replace Go matrix versions 1.24/1.25 (don't exist) with 1.22/1.23
  • Upgrade setup-go@v4 to @v5 in both test and lint jobs
  • Replace bc-based coverage threshold check (not reliably on runners) with portable awk

reconciliation-ci.yml

  • Upgrade setup-go@v4 to @v5

benchmarks.yml: remove duplicate Enforce benchmark thresholds step and
merge threshold summary into single step; fix baseline artifact path
from non-existent new.txt to handlers_new.txt and subscriptions_new.txt;
upgrade security job from checkout@v3 and setup-go@v4 to v4 and v5

fuzz.yml: remove 3 dangling job refs fuzz-swap-exact-in,
fuzz-swap-exact-out, fuzz-swap-raw-body from fuzz-summary needs array
that have no corresponding jobs and cause the workflow to always fail

test-jwt-hardening.yml: replace non-existent Go 1.24 and 1.25 matrix
versions with 1.22 and 1.23; upgrade setup-go@v4 to v5 in both jobs;
replace bc-based coverage comparison with portable awk

reconciliation-ci.yml: upgrade setup-go@v4 to v5
@Masked18

Copy link
Copy Markdown
Owner Author

Closing to reopen against upstream main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants