chore(deps): update build-tools digest to 5307281

[red-hat-konflux]

This PR contains the following updates:

Package	Update	Change
build-tools (changelog)	digest	8b1653c → 5307281

---

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 becomes conflicted, 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.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Updated the underlying build tooling to a newer version.

Walkthrough

The build-tools submodule reference changes from commit 6bdef6f... to 8b1653c....

Changes

Build tools

Layer / File(s)	Summary
Update build-tools reference build-tools	The submodule commit pointer is updated to 8b1653c4....

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: aferd, apinkert, bannermanj

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is on-topic but does not follow the required template and omits the summary, UI information, screenshots, checklist, and issue link.	Use the repository template and add the required summary, UI impact information, screenshots, checklist, and applicable issue link.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the build-tools digest update, which is the primary change in the pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/master/build-tools-digest

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@build-tools`:
- Line 1: Update the build-tools gitlink from
8b1653c4a18b3b67fc28bbb4cb9d2b67950d0637 to the requested commit, ensuring the
submodule reference includes the intended build-tools changes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 75392377-320a-4a17-a561-2d9a7dd42a4b

📥 Commits

Reviewing files that changed from the base of the PR and between 09e55dc and 3b00221.

📒 Files selected for processing (1)

• build-tools

[coderabbitai]

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Repo root: '; pwd
printf '\nTop-level files around build-tools:\n'
git ls-files --stage -- build-tools || true

printf '\nRecent diff for build-tools (stat only):\n'
git diff --stat -- build-tools || true

printf '\nSubmodule status if available:\n'
git submodule status -- build-tools || true

printf '\nSearch for references to e6caefc and 8b1653c:\n'
rg -n --hidden --no-messages 'e6caefc|8b1653c4a18b3b67fc28bbb4cb9d2b67950d0637|8b1653c' .

Repository: RedHatInsights/sources-ui

Length of output: 467

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '--- .gitmodules ---\n'
if [ -f .gitmodules ]; then cat -n .gitmodules; else echo 'no .gitmodules'; fi

printf '\n--- build-tools entry details ---\n'
git config -f .gitmodules --get-regexp 'submodule\.build-tools\..*' || true

printf '\n--- any local refs mentioning build-tools URL or target SHAs ---\n'
rg -n --hidden --no-messages 'build-tools|e6caefc|8b1653c' .gitmodules .git config .github . || true

Repository: RedHatInsights/sources-ui

Length of output: 254

---

🌐 Web query:

RedHatInsights insights-frontend-builder-common e6caefc 8b1653c build-tools commit

💡 Result:

The references to e6caefc and 8b1653c relate to updates of the build-tools Git submodule within repositories that use the RedHatInsights/insights-frontend-builder-common repository [1][2][3]. Repositories in the RedHatInsights ecosystem use a build-tools submodule to point to specific versions (commits) of the shared builder common repository [1][4]. Updates to these build tools are standard maintenance tasks, often labeled as chore(deps) commits or pull requests [2][4][5]. These updates modify the Git submodule pointer to track a different upstream commit, allowing projects to consume the latest shared build tooling, configuration, or dependency updates without requiring changes to the project's own application code or configuration [2][4][5]. For example, pull request #3485 in the insights-chrome repository explicitly updated the build-tools digest to 8b1653c [2]. Such changes are routine and ensure that all frontend applications building on cloud.redhat.com utilize consistent, updated build infrastructure [1][2][4].

Citations:

• 1: https://github.com/RedHatInsights/insights-frontend-builder-common
• 2: chore(deps): update build-tools digest to 7985cc5 insights-chrome#3485
• 3: https://github.com/RedHatInsights/insights-frontend-builder-common/blob/master/README.md
• 4: chore(deps): update build-tools digest to 7c82774 (master) insights-inventory-frontend#3393
• 5: RedHatInsights/learning-resources@60d7a1e

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '--- .gitmodules ---\n'
if [ -f .gitmodules ]; then cat -n .gitmodules; else echo 'no .gitmodules'; fi

printf '\n--- build-tools entry details ---\n'
git config -f .gitmodules --get-regexp 'submodule\.build-tools\..*' || true

printf '\n--- any local refs mentioning build-tools URL or target SHAs ---\n'
rg -n --hidden --no-messages 'build-tools|e6caefc|8b1653c' .gitmodules .github . || true

Repository: RedHatInsights/sources-ui

Length of output: 254

---

Point build-tools at the requested commit. The gitlink still points to 8b1653c4a18b3b67fc28bbb4cb9d2b67950d0637, so the build-tools update the PR intends isn't in place yet.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@build-tools` at line 1, Update the build-tools gitlink from
8b1653c4a18b3b67fc28bbb4cb9d2b67950d0637 to the requested commit, ensuring the
submodule reference includes the intended build-tools changes.

Source: MCP tools

.