ci: bump ec2-github-runner pin to v4.0.2 (#68/#69) - #291
Merged
Conversation
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>
🔐 Security scan summaryCommit
📦 Dependencies
Vulnerabilities (Trivy, top 50)
📎 Full machine-readable reports are attached to this run as artifacts: |
Codecov Report✅ All modified and coverable lines are covered by tests. 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. 🚀 New features to boost your workflow:
|
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.
What
Bumps the pinned
namecheap/ec2-github-runnerSHA from65fbe4f(v4.0.1) to54ee3e4(v4.0.2, newly cut) in all four pin sites:ci.yml's start-runner and stop-runner steps, and both passes incleanup-ec2-runners.yml.Why now
v4.0.1 predates two merged fixes on the action repo that neither had a release tag yet:
mode: stopnow waits for the instance to actually reachstoppedbefore returning (StopInstancesalone only moves it tostopping). This is the action-side half of the stopping-state race ci: wait out the stopping-state warm-pool race; move nightly drain to 23:07 UTC #290 fixed workflow-side in this repo on 2026-07-10 (a tightly-queued run saw an empty warm pool and cold-launched a duplicate instance).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 baremaincommit — release notes.Validation
actionlintclean on both workflow files.