Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[quality] refresh-radar-reports.yml runs on ubuntu-latest while every other job pins ubuntu-24.04

Closed Beginner friendly
#881 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
90/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, javascript, yaml
Domain
ci-cd

Research direction

Update .github/workflows/refresh-radar-reports.yml line 17 to use the pinned runner, ubuntu-24.04. Then remove the corresponding baseline entry from tests/ci-supply-chain.test.mjs and run that test to confirm the floating-runner exception is no longer needed.

Written by the indexing model from the issue text.

Description

agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing

Finding

.github/workflows/refresh-radar-reports.yml is the only workflow in the repository that names a floating runner label:

$ grep -rn "runs-on" .github/workflows/
.github/workflows/refresh-radar-reports.yml:17:    runs-on: ubuntu-latest

All 11 other jobs pin ubuntu-24.04: architecture-submission.yml:27, ci.yml:23/81/103, codeql.yml:46, create-milestones.yml:18, deploy-gh-pages.yml:21/101, import-architectures.yml:18, pr-queue-hygiene.yml:14, refresh-community-people.yml:17.

GitHub re-points ubuntu-latest at a new image on its own schedule. This job is scheduled, commits data back to the repository, and is the one job whose runner can change underneath it without a commit here — so a failure (or, worse, a silently different node/OpenSSL/CA set while it fetches and rewrites data/radar-reports.json) arrives detached from any change anyone made. The repository has already decided it wants pinned images; this line is the single outlier.

Recommendation

Replace line 17 of .github/workflows/refresh-radar-reports.yml:

    runs-on: ubuntu-latest

with:

    runs-on: ubuntu-24.04

Then, in the same change, delete the baseline entry that records this gap in tests/ci-supply-chain.test.mjs:

const KNOWN_FLOATING_RUNNERS = new Set([refresh-radar-reports.yml:
---
🐝 **Hive Agent**: `quality` | **Instance:** `hosted-available-lke648397-260827-5n31` | **SHA:** `ff93581`

— hive: agent=quality backend=copilot model=claude-opus-5 copilot=1.0.88
Dominant language
JavaScript
Stars
0
Forks
3
Avg merge
7h 21m
Merged PRs (30d)
575

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.