chore(deps): update pip requirements

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
pip-tools (changelog)	==7.5.0 -> ==7.5.1
ruamel.yaml	==0.18.15 -> ==0.18.16
setuptools-scm	==9.2.0 -> ==9.2.2

---

Release Notes

jazzband/pip-tools (pip-tools)

v7.5.1

Compare Source

2025-09-26

Bug fixes

• Fixed static parsing of {file}pyproject.toml data when the
  {file}pyproject.toml is supplied as a relative path -- by {user}sirosen.

  PRs and issues: {issue}2215, {issue}2221, {issue}2233

• The "via" paths in pip-compile output for requirements discovered from
  pyproject.toml data are now written in POSIX format -- by {user}sirosen.

  PRs and issues: {issue}2221

• Fixed a bug which removed slashes from URLs in -r and -c in the output
  of pip-compile -- by {user}sirosen.

  PRs and issues: {issue}2223

• Fixed an incompatibility with click >= 8.3 which made pip-compile display incorrect
  options in the compile command in output headers -- by {user}sirosen.

  PRs and issues: {issue}2235

Features

• pip-tools now officially supports pip version 25.2 -- by {user}sirosen.

  PRs and issues: {issue}2214

Improved documentation

• ReadTheDocs builds for pip-tools no longer include htmlzip and pdf outputs -- by {user}sirosen.

  PRs and issues: {issue}2218

Contributor-facing changes

• pip-tools now tests on pip version 25.2 -- by {user}sirosen.

  PRs and issues: {issue}2214

• The changelog documentation for contributors now provides hyperlinks to the source of each example change note -- by {user}jayaddison (for OpenCulinary).

  PRs and issues: {issue}2217

• The CPython versions tested in nightly CI runs are now separate from
  branch and PR CI, and don't include very old versions -- by {user}sirosen.

  PRs and issues: {issue}2226

pypa/setuptools-scm (setuptools-scm)

v9.2.2

Compare Source

Fixed

• fix #​1231: don't warn about tool.setuptools.dynamic.version when only using file finder.
  The warning about combining version guessing with setuptools dynamic versions should only
  be issued when setuptools-scm is performing version inference, not when it's only being
  used for its file finder functionality.

v9.2.1

Compare Source

Fixed

• fix #​1216: accept and create a warning for usages of version = attr: in setuptools config.
  unfortunately dozens of projects cargo-culted that antipattern

---

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.

This PR has been generated by MintMaker (powered by Renovate Bot).

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign luisjira for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

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

I'm waiting for a github.com 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.

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.