chore(deps): update module github.com/prometheus/procfs to v0.21.1

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/prometheus/procfs	v0.21.0 → v0.21.1

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

prometheus/procfs (github.com/prometheus/procfs)

v0.21.1

Compare Source

What's Changed

• Fix invalid format strings by @​HNO3Miracle in #​832

New Contributors

• @​HNO3Miracle made their first contribution in #​832

Full Changelog: prometheus/procfs@v0.21.0...v0.21.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

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 5:21 PM UTC · Completed 5:25 PM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-review]

Review — ✅ Approve

PR: #312 — chore(deps): update module github.com/prometheus/procfs to v0.21.1
Author: red-hat-konflux[bot] (automated dependency update)
Changes: go.mod, go.sum (3 additions, 3 deletions)

Summary

Routine patch-version bump of an indirect dependency (github.com/prometheus/procfs v0.21.0 → v0.21.1). The upstream release contains a single fix for invalid format strings (prometheus/procfs#832). No application code is modified.

Analysis

Dimension	Result
Correctness	✅ Mechanical version bump; no logic changes
Security	✅ No new dependencies; patch-level bug fix only
Intent & scope	✅ Automated dependency update, properly scoped to go.mod / go.sum
Style & conventions	✅ Standard Go module update format
Documentation	✅ No documentation impact
Cross-repo contracts	✅ No API surface changes

No findings.

Previous run

Looks good to me

Previous run (2)

Looks good to me

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 5:24 AM UTC · Completed 5:28 AM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-retro]

Retro: PR #312 — Automated dependency bump (prometheus/procfs v0.21.0 → v0.21.1)

Workflow went smoothly. This was a trivial bot-authored dependency bump PR (go.mod + go.sum only) by MintMaker/Renovate. The review agent correctly approved it in ~6.5 minutes, labeled it ready-for-merge, and posted no inline findings. The PR was later autoclosed by the bot (~36 hours later) — typical MintMaker lifecycle behavior. No human interaction occurred.

Improvement opportunities identified (all already tracked)

Two efficiency improvements apply but are already covered by existing open issues:

1. Skip retro on autoclosed bot PRs — Running a full retro on an autoclosed dependency bump with zero human interaction and no code agent involvement is pure token waste. Already tracked by #2461 (skip retro for autoclosed bot PRs), #2739, #2638, and #2749 (unify skip conditions).

2. Fast-path review for trivial bot dependency bumps — The review agent spent ~6.5 minutes on a 4-line go.mod/go.sum change. A lightweight review path could reduce both time and token cost. Already tracked by #1358 (lightweight review path), #2639 (fast-path in orchestrator), and #2842 (cheaper model for trivial PRs).

No new proposals warranted — the existing issue coverage is comprehensive.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 9:39 AM UTC · Completed 9:43 AM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 1:13 PM UTC · Completed 1:18 PM UTC
Commit: 14477fe · View workflow run →

[fullsend-ai-retro]

PR #312 is a trivial Renovate bot dependency bump (prometheus/procfs v0.21.0 → v0.21.1, 3+3 lines in go.mod/go.sum) that was never merged and had zero human engagement. The MintMaker bot's close-reopen-close cycle generated 4 agent runs total: 2 reviews and 2 retros. This current run is the second retro on the same PR — the first retro (Jul 5) already correctly concluded there was nothing to learn. All waste patterns are covered by existing open issues (#2401, #2461, #3317, #963, #1355). Filing one evidence issue linking this instance to the duplicate-retro tracker.

Proposals filed

• Evidence for #2401: second retro on smee-sidecar PR #312 reproduces identical zero-value conclusion 3 days after first retro (in fullsend-ai/fullsend)

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 6:09 PM UTC · Completed 6:12 PM UTC
Commit: 14477fe · View workflow run →

[yftacherzog]

Closing: renovate.json was updated to disable Renovate updates for indirect-only Go module dependencies (matchManagers: gomod, matchDepTypes: indirect, enabled: false). These transitive deps are resolved via go mod tidy when direct dependencies change, so standalone indirect update PRs are no longer expected.

— Yftach's Cursor

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 8:41 AM UTC · Completed 8:46 AM UTC
Commit: 14477fe · View workflow run →

[fullsend-ai-retro]

Retro Analysis for PR #312

The retro agent was unable to analyze PR #312 in detail because the sandbox environment blocks outbound HTTPS connections to the GitHub API (the proxy at 10.200.0.1:3128 returns HTTP 403 on CONNECT tunnels to api.github.com). Combined with a depth-1 git clone that only contains commit #323, the agent had no way to read the PR's diff, comments, reviews, or timeline.

This is a blocking infrastructure issue that prevents the retro agent from performing any meaningful analysis on any PR.

Proposal filed

1. Retro agent needs GitHub API access or pre-fetched PR context — The sandbox must either allowlist GitHub API through the proxy or pre-fetch PR metadata before the agent starts.

Proposals filed

• Retro agent cannot access GitHub API — sandbox proxy blocks all outbound HTTPS (in fullsend-ai/fullsend)

[red-hat-konflux]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v0.21.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.