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

Revert ubuntu-26.04 in fullsend.yaml and disable Renovate github-runner manager

Open Beginner friendly
  • Is something wrong?
#301 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Read .github/workflows/fullsend.yaml and .github/renovate.json5, then compare runner references with .github/workflows/prioritize.yml. Revert the stop-fix runner to ubuntu-24.04 and disable Renovate's github-runner manager. Done when the scaffolded workflow references align and Renovate configuration disables that manager; the issue also asks for dashboard and follow-up verification.

Written by the indexing model from the issue text.

Description

bug infra ready-for-triage triaged

What happened

In PR #300, Mend Renovate (hermes-renovate[bot]) opened a dependency update proposing chore(deps): update dependency ubuntu to v26, modifying .github/workflows/fullsend.yaml.

Renovate's built-in github-runner manager detected runs-on: ubuntu-24.04 in the stop-fix job and updated it to runs-on: ubuntu-26.04. However, Renovate did not detect or update the custom workflow input runner_image: ubuntu-24.04 passed to reusable-dispatch.yml under the dispatch job in the same file, nor the matching runner_image: ubuntu-24.04 input in .github/workflows/prioritize.yml. All native ProtoBot CI workflows (ci-workflow.yaml, renovate.yaml) use runs-on: ubuntu-latest.

Because Renovate classified the 24.04 to 26.04 bump as a major version upgrade, platform automerge was disabled per .github/renovate.json5 (matchUpdateTypes: ["patch", "minor"]). Fullsend review was skipped due to the branch filter on renovate/*, and CodeRabbit skipped review because the author was a bot. Maintainer John Strunk silently approved and merged the PR. The modified stop-fix job was never executed or verified during CI because its execution is gated on /fs-fix-stop issue comments.

What could go better

Scaffolded workflow files like .github/workflows/fullsend.yaml and .github/workflows/prioritize.yml are platform-managed artifacts with explicit headers (# This file is managed by fullsend. Do not edit it directly.). Upstream Fullsend manages runner image versions uniformly across shim templates via the __GH_RUNNER__ placeholder.

Allowing Renovate's github-runner manager to update individual runs-on: keys causes two issues:

  1. Version skew within scaffolded workflows: stop-fix was bumped to ubuntu-26.04 while dispatch and prioritize.yml remain on ubuntu-24.04.
  2. Unnecessary human review burden: Because major version upgrades are excluded from automerge, maintainers must manually review and merge standalone runner upgrades that only partially apply to platform shims and are never exercised by the repo's regular CI suite.

Because ProtoBot's native workflows use ubuntu-latest, the github-runner manager only ever touches Fullsend shims. Disabling this manager in .github/renovate.json5 avoids uncoordinated runner updates, leaving runner versioning to Fullsend platform upgrades.

Proposed change

  1. In .github/workflows/fullsend.yaml, revert line 94 runs-on: ubuntu-26.04 back to runs-on: ubuntu-24.04 to restore parity with the dispatch job (runner_image: ubuntu-24.04) and .github/workflows/prioritize.yml (runner_image: ubuntu-24.04).

  2. In .github/renovate.json5, add a configuration rule to disable the github-runner manager:

    {
      "description": "Disable GitHub runner version updates on scaffolded Fullsend workflows",
      "matchManagers": ["github-runner"],
      "enabled": false,
    },

Alternatively, set "github-runner": { "enabled": false } at the root of .github/renovate.json5.

This ensures runner versions in scaffolded shims stay aligned with upstream platform releases rather than ad-hoc Renovate bumps.

Validation criteria

  1. Verify .github/workflows/fullsend.yaml and .github/workflows/prioritize.yml consistently reference ubuntu-24.04 across all jobs and runner inputs.
  2. In the repository Dependency Dashboard (redhat-et/ProtoBot#9), verify that Renovate no longer detects or proposes ubuntu runner updates under github-actions.
  3. Over the next 90 days, verify that no automated PRs are opened modifying runs-on: in .github/workflows/fullsend.yaml.

Generated by retro agent from https://github.com/redhat-et/ProtoBot/pull/300

Dominant language
Go
Stars
6
Forks
8
Avg merge
1d 7h
Merged PRs (30d)
82

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 redhat-et/ProtoBot

All issues in redhat-et/ProtoBot

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.