don't register the runner if the version is not allowed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the bug
It seems that an outdated runner is very able to register. Which it can do in a loop. And then exhaust every available runner registration.
It seems to me that GHA infrastructure should just... not register the invalid runner at all, but I suspect it will be easier to effect change here.
Could the runner find out if it's a supported version and bail before even trying to register if it's too old?
To Reproduce
Steps to reproduce the behavior:
- Run a runner, set it to auto-restart on any failure
- Let it go a bit stale
Expected behavior
GHA to... reject invalid runners rather than register a runner that is, de facto, useless.
Runner Version and Platform
n/a
OS of the machine running the runner? OSX/Windows/Linux/... Linux
What's not working?
n/a
Job Log Output
n/a
Runner and Worker's Diagnostic Logs
n/a
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the runner's version validation and registration path, then reproduce with an outdated runner configured to restart after failure. Done means an unsupported runner exits before registration and cannot repeatedly consume runner-registration capacity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100