Skip to content

ci: bump ec2-github-runner pin to v4.0.2 (#68/#69) - #291

Merged
kurok merged 1 commit into
masterfrom
ci/bump-ec2-runner-pin-69
Jul 10, 2026
Merged

ci: bump ec2-github-runner pin to v4.0.2 (#68/#69)#291
kurok merged 1 commit into
masterfrom
ci/bump-ec2-runner-pin-69

Conversation

@kurok

@kurok kurok commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator

What

Bumps the pinned namecheap/ec2-github-runner SHA from 65fbe4f (v4.0.1) to 54ee3e4 (v4.0.2, newly cut) in all four pin sites: ci.yml's start-runner and stop-runner steps, and both passes in cleanup-ec2-runners.yml.

Why now

v4.0.1 predates two merged fixes on the action repo that neither had a release tag yet:

Since v4.0.1 had no tag covering either fix, I cut and pushed v4.0.2 on the action repo at 54ee3e4 (both fixes included) rather than pinning to a bare main commit — release notes.

Validation

  • actionlint clean on both workflow files.
  • Diff is exactly the four pin-line replacements — no other content touched.
  • Next CI run on this repo exercises the new pin directly (start-runner + stop-runner); next scheduled cleanup run exercises it for both cleanup passes.

v4.0.1 (65fbe4f) predates two merged fixes: #68 (start step now
requires multiple consecutive online polls before declaring success,
closing a leaked-running-instance risk from a flapping warm-restart
registration) and #69 (mode:stop now waits for the actual stopped
state before returning, closing the race this repo hit on 2026-07-10
where a tightly-queued run saw an empty warm pool and cold-launched a
duplicate instance).

Cut and pushed the v4.0.2 tag on namecheap/ec2-github-runner at
54ee3e4 to cover both, then repointed all four pin sites (ci.yml
start-runner + stop-runner, cleanup-ec2-runners.yml both passes).

Signed-off-by: yuriyryabikov <22548029+kurok@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown

🔐 Security scan summary

Commit b3a8e455 · branch ci/bump-ec2-runner-pin-69 · generated 2026-07-10 17:37 UTC

Scan Gate Findings
Trivy — vulnerabilities (SCA) 🔴 0 critical · 🟠 0 high · 🟡 0 medium · ⚪ 0 low · 1 unknown
Trivy — IaC misconfig 0 failing
Trivy — secrets 0 detected
Trivy — licenses 0 policy finding(s)
govulncheck (reachability) 0 reachable · 0 imported-only
CodeQL (code scanning, open) 0 open · 🔴 0 critical · 🟠 0 high

Gate (blocks merge): HIGH/CRITICAL fixable CVEs · reachable Go vulnerabilities · forbidden licenses · committed secrets. Counts above are the full picture (incl. medium/low and unfixed), so they can exceed what actually gates. CodeQL is informational here. ✅ = gate job passed, ❌ = failed, ⚪ = skipped.

📦 Dependencies

  • SBOM components (CycloneDX): 64
  • Go modules in go.mod: 6 direct · 56 indirect
Vulnerabilities (Trivy, top 50)
Severity ID Package Installed Fixed
UNKNOWN GO-2026-5932 golang.org/x/crypto v0.53.0

📎 Full machine-readable reports are attached to this run as artifacts: security-summary, trivy-json, govulncheck-json, sbom-cyclonedx.

@codecov

codecov Bot commented Jul 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.22%. Comparing base (de8a8e9) to head (b3a8e45).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #291   +/-   ##
=======================================
  Coverage   89.22%   89.22%           
=======================================
  Files          15       15           
  Lines        1643     1643           
=======================================
  Hits         1466     1466           
  Misses        111      111           
  Partials       66       66           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@kurok
kurok merged commit 742b97c into master Jul 10, 2026
25 checks passed
@kurok
kurok deleted the ci/bump-ec2-runner-pin-69 branch July 10, 2026 17:52
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.

1 participant