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

Group fullsend and agents package updates in Renovate configuration

Open Beginner friendly
  • Is something wrong?
#277 0 comments 0 reactions 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
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, yaml
Domain
devops

Research direction

Read .github/renovate.json5 and inspect the existing packageRules and postUpgradeTasks rule for fullsend-ai/agents. Add the described group for fullsend-ai/fullsend and fullsend-ai/agents, then verify the existing post-upgrade task still matches the combined group branch. Done when Renovate groups both dependency updates into one PR and the repository configuration remains valid.

Written by the indexing model from the issue text.

Description

ready-for-triage

What happened

During the v0.45.0 release cycle, Renovate opened two distinct PRs within seconds of each other: PR #274 updating fullsend-ai/agents in .fullsend/harness/*.yaml, and PR #275 updating fullsend-ai/fullsend reusable workflow references in .github/workflows/fullsend.yaml and .github/workflows/prioritize.yml. Both PRs progressed independently through CI, were placed into separate merge queue slots, and merged separately into main. Each merge triggered an independent retrospective workflow run (run 38335212484 and run 38335212276).

What could go better

High confidence. fullsend-ai/fullsend and fullsend-ai/agents are co-versioned upstream and tightly coupled. For instance, Fullsend v0.45.0 release notes highlight that harnesses extending fullsend-ai/agents via base: log reserved-name warnings until bumped to an agents commit that uses bare provider names. Splitting these dependencies across separate PRs creates temporary version skew where workflows and harnesses are on mismatched minor versions. Furthermore, separate PRs duplicate CI runs, merge queue latency, and retro agent dispatches. .github/renovate.json5 already establishes grouping for coupled tools (e.g., skillsaw).

Proposed change

In .github/renovate.json5, add a packageRules entry grouping fullsend-ai/fullsend and fullsend-ai/agents under groupName: "fullsend":

{
  "description": "Group fullsend action and harness updates",
  "groupName": "fullsend",
  "matchPackageNames": [
    "fullsend-ai/fullsend",
    "fullsend-ai/agents",
  ],
}

Verify that the existing matchPackageNames: ["fullsend-ai/agents"] postUpgradeTasks rule continues to run on the combined group branch.

Validation criteria

  1. The next release of Fullsend and Agents generates a single combined Renovate PR updating both .github/workflows/*.yaml actions and .fullsend/harness/*.yaml base pins.
  2. Version updates to the fullsend ecosystem incur only a single CI execution, one merge queue entry, and one retrospective run.
  3. The repository avoids intermediate commits where workflow action versions and agent harness overlays are on differing releases.

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

Dominant language
Go
Stars
6
Forks
6
Avg merge
20h 4m
Merged PRs (30d)
90

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.