chore(deps): Update CI client image

[red-hat-konflux]

This PR contains the following updates:

Package	Update	Change
hashicorp/terraform	patch	1.15.4 → 1.15.5
openshift/rosa	patch	1.2.62 → 1.2.63

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

hashicorp/terraform (hashicorp/terraform)

v1.15.5

Compare Source

1.15.5 (May 27, 2026)

ENHANCEMENTS:

• Support for module version evaluating to null (in the context of dynamic module sources) (#​38632)

BUG FIXES:

• Fix crash on init for modules with empty source (#​38628)

openshift/rosa (openshift/rosa)

v1.2.63

Compare Source

Changelog

Bug fixes

• dde051c OCM-00000 | fix(ci): stabilize e2e image builds
• a8ea7d8 OCM-00000 | fix(ci): trust e2e git worktree
• 9c6b7a2 OCM-24123 | fix: Refactor proxy URL validation logic
• 41de661 OCM-24858 | fix: default machinepools to m7i.xlarge

Others

• eee232b OCM-24070 | chore: Set release version to 1.2.62
• 2ab4c96 OCM-24858 | test: pin machinepool e2e default expectation
• 3e40b4e OCM-00000 | chore: Set release version to 1.2.63-RC1
• 173fa2f OCM-00000 | chore: Set release version to 1.2.63

---

Configuration

📅 Schedule: 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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.

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a terraform-redhat member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[coderabbitai]

Walkthrough

The PR updates pinned tool versions in the Dockerfile used by CI/integration Prow clients. Terraform is bumped from 1.15.4 to 1.15.5, and ROSA is bumped from 1.2.62 to 1.2.63. All installation flows and base images remain unchanged.

Changes

CI Tool Version Updates

Layer / File(s)	Summary
Tool version bumps Dockerfile	Terraform build argument updated from 1.15.4 to 1.15.5; ROSA build argument updated from 1.2.62 to 1.2.63. Installation mechanisms and base image remain the same.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

approved, lgtm

Suggested reviewers

• marcolan018
• davidleerh
• jerichokeyne

🚥 Pre-merge checks | ✅ 4 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	PR description lacks required sections (PR Summary, Detailed Description, Type of Change checkbox, Testing steps, verification checklist) per template.	Fill in all required template sections: PR Summary, Detailed Description explaining why the updates are needed, check the appropriate Type of Change box, provide testing instructions, and complete the Developer Verification Checklist.
Pr Checklist Claims Vs Evidence (Generic)	❓ Inconclusive	Cannot access the actual PR body text from the repository to verify checked checklist items; only the template is available in the codebase.	Verification requires access to the actual PR description with filled-in Developer Verification Checklist items; check the GitHub PR #156 directly for the PR body content.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating CI client image dependencies in the Dockerfile.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/main/ci-client-image

---

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

[openshift-ci]

@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/rosa-hcp-private	b9b1b5d	link	true	/test rosa-hcp-private
ci/prow/rosa-hcp-public	b9b1b5d	link	true	/test rosa-hcp-public

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[amandahla]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amandahla, red-hat-konflux[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [amandahla]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[amandahla]

Closing so Renovate can get the new changes and open a new pr