Migrate Renovate config

[red-hat-konflux]

The Renovate config in this repository needs migrating. Typically this is because one or more configuration options you are using have been renamed.

You don't need to merge this PR right away, because Renovate will continue to migrate these fields internally each time it runs. But later some of these fields may be fully deprecated and the migrations removed. So it's a good idea to merge this migration PR soon.

🔕 Ignore: Close this PR and you won't be reminded about config migration again, but one day your current config may no longer be valid.

❓ Got questions? Does something look wrong to you? Please don't hesitate to request help here.

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:28 PM UTC · Completed 3:32 PM UTC
Commit: 47d3320 · View workflow run →

[fullsend-ai-review]

Review — ✅ Approve

PR: #3353 — Migrate Renovate config
Author: red-hat-konflux[bot]
Scope: 1 file changed (renovate.json), +3 / −1

Summary

This PR migrates the Renovate configuration field fileMatch to its successor managerFilePatterns, as prompted by the Renovate bot itself. The migration is straightforward and correct:

• The deprecated fileMatch key is replaced with managerFilePatterns
• The regex pattern \.tekton/.*\.yaml$ is correctly wrapped in / delimiters (required by managerFilePatterns to distinguish regex patterns from glob patterns)
• The regex semantics are unchanged — the same .tekton/*.yaml files will be matched

Dimension Results

Dimension	Result
Correctness	✅ Migration syntax is correct. No stale fileMatch references elsewhere in the repo.
Security	✅ No secrets, injection vectors, or permission changes. Config-only change.
Intent & Coherence	✅ Mechanical bot-generated change. Authorization implicit from nature of change.
Style & Conventions	✅ No findings. Follows existing JSON formatting.
Documentation	✅ No stale Renovate fileMatch references in repo documentation.
Cross-repo Contracts	⏭ Skipped — no exported APIs or interfaces modified.

Notes

Other Renovate deprecated fields (customType, datasourceTemplate) remain in the config. These are still functional and Renovate will continue to migrate them internally at runtime. If Renovate raises a follow-up migration PR for these fields, it can be handled then.

Previous run

Looks good to me

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	53.62% <ø> (ø)
generative	17.18% <ø> (ø)
integration	28.36% <ø> (ø)
unit	71.74% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[simonbaird]

Needs a rebase probably.

[simonbaird]

Rebased.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 9:13 PM UTC · Completed 9:21 PM UTC
Commit: 87c4a29 · View workflow run →

[robnester-rh]

/fs-fix rebase on top of main and resolve conflicts

[fullsend-ai-coder]

🤖 Fix · ⚠️ Cancelled · Started 2:13 PM UTC · Ended 2:14 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-coder]

🤖 Finished Fix · ✅ Success · Started 2:15 PM UTC · Completed 2:20 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-coder]

🔧 Fix agent — iteration 1 (human-triggered)

Successfully rebased konflux/mintmaker/migrate-config onto origin/main (168 commits behind). Resolved merge conflict in renovate.json by accepting main's version — the customManagers section was removed from main, so the fileMatch-to-managerFilePatterns migration is no longer needed. The PR branch now has no diff from main and can be closed.

Fixed (1):

1. rebase on top of main and resolve conflicts: Rebased the branch onto origin/main. Resolved the merge conflict in renovate.json by accepting main's version. The customManagers section (which the PR was migrating from fileMatch to managerFilePatterns) was removed from main in a prior commit, making the migration unnecessary. The original PR commit was dropped during rebase as it produced an empty diff after conflict resolution. The branch now has no diff from main — this PR can be closed.

Tests: passed

Next steps:

• /fs-review — request a re-review of the changes
• /fs-fix <your instruction> — run another fix pass with specific guidance
• Push commits directly — review re-runs automatically on push
  _{Updated by fullsend fix agent}

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:21 PM UTC · Completed 2:24 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

Review skipped — this PR is already merged.

The /fs-review command only reviews open pull requests.

_{Posted by fullsend pre-review check}

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 2:22 PM UTC · Completed 2:28 PM UTC

Commit: 87c4a29 · View workflow run →

[fullsend-ai-review]

Review skipped — this PR is already merged.

The /fs-review command only reviews open pull requests.

_{Posted by fullsend post-review check}

[fullsend-ai-retro]

Retro: PR #3353 — Migrate Renovate config

Outcome: A Renovate config migration PR sat open for 63 days, was rebased by the fix agent into a zero-diff state, and then auto-merged as a no-op due to a race condition. The workflow was functional but produced avoidable waste.

Timeline

1. Jun 22: Renovate bot opened PR to migrate fileMatch → managerFilePatterns in renovate.json.
2. Jun 22: Review agent approved with a thorough dimension-based review — correct assessment of a straightforward config migration.
3. Jul 13: Human (simonbaird) approved, noted rebase needed, and rebased the PR. Auto-merge was enabled.
4. Jul 13: Review agent re-ran and approved again (triggered by the rebase push).
5. Aug 24: Human (robnester-rh) triggered /fs-fix rebase on top of main and resolve conflicts — the branch was 168 commits behind main.
6. Aug 24: Fix agent ran, rebased successfully, resolved the merge conflict by accepting main's version (the customManagers section had been removed from main in a prior commit). This made the entire migration moot — zero diff from main.
7. Aug 24: Fix agent posted "can be closed" but force-pushed the zero-diff branch. Auto-merge (enabled since Jul 13) fired within 2 seconds, merging a PR with 0 additions, 0 deletions, 0 changed files.
8. Aug 24: Review agent dispatched on the merged PR, only to skip — wasted workflow run.

Assessment

The review agent performed well on both reviews — the initial approval was thorough and correctly identified the migration as safe. The fix agent's rebase and conflict resolution logic was sound. The breakdown was in the post-fix workflow: the fix agent recognized the zero-diff state (recommending closure) but didn't act on it, and the post-script force-pushed without disabling auto-merge first, causing a no-op merge.

All identified improvements map to existing open issues — no new proposals needed:

• Fix agent should close PR when fix reverts all changes to empty diff fullsend-ai/fullsend#2585 — Fix agent should close PR when fix produces empty diff. This retro provides additional evidence: the fix agent correctly diagnosed "can be closed" but the post-script still force-pushed and reported success, allowing auto-merge to merge a zero-diff PR.
• Fix agent post-script should detect zero-commit outcomes and report a warning instead of success fullsend-ai/fullsend#3419 — Fix agent post-script should detect zero-commit outcomes and report a warning. Here the fix agent reported success despite producing no meaningful changes.
• Dispatch routing should check PR merged state before dispatching review for opened/synchronize events fullsend-ai/fullsend#4070 — Dispatch routing should check PR merged state before dispatching review. The post-merge review dispatch at 14:21 was wasted.
• Skip review dispatch when PR has zero changed files fullsend-ai/fullsend#2476 — Skip review dispatch when PR has zero changed files. The PR had 0 changed files at merge time.

One nuance worth noting for #2585: the current proposal describes a post-push check, but this retro shows the check (or at minimum, disabling auto-merge) must happen before the force-push to prevent the race condition. If auto-merge fires during the 2-second window between push and close, the PR gets merged as a no-op.