chore(deps): update pip requirements

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
click (changelog)	==8.3.0 -> ==8.3.1
pip-tools (changelog)	==7.5.1 -> ==7.5.2
ruamel.yaml.clib	==0.2.14 -> ==0.2.15

---

Warning

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

---

Release Notes

pallets/click (click)

v8.3.1

Compare Source

jazzband/pip-tools (pip-tools)

v7.5.2

Compare Source

2025-11-11

Bug fixes

• Fixed pip-compile to handle relative path includes which are not subpaths of
  the current working directory -- by {user}sirosen.

  PRs and issues: {issue}2231, {issue}2260

• Using --upgrade-package and dynamically building project metadata no
  longer causes an {exc}AttributeError when pip encounters an error during the
  build -- by {user}Epic_Wink and {user}tusharsadhwani.

  PRs and issues: {issue}2258

Features

• Test and declare Python 3.13 support -- by {user}jayaddison (for OpenCulinary).

  PRs and issues: {issue}2251

• pip-tools is now compatible with pip 25.3 -- by {user}shifqu.

  PRs and issues: {issue}2252, {issue}2253

Packaging updates and notes for downstreams

• pip-tools now supports installation from git archives by providing
  setuptools-scm with .git_archival.txt data.

  PRs and issues: {issue}2225

Contributor-facing changes

• The change log entry bot has been explicitly configured to stop requiring
  news fragments in pull requests having the bot:chronographer:skip label set
  -- by {user}sirosen and {user}webknjaz.

  It was also set up to reference our change log authoring document from the
  GitHub Checks pages. And the reported check name is now set to Change log entry.

  PRs and issues: {issue}2201

• The CI is now set up to invoke failed tests again with
  maximum level of detail -- by {user}webknjaz.

  The change is aimed at helping troubleshoot failures
  that might be difficult to reproduce locally.

  PRs and issues: {issue}2254

• The integration with Codecov has been updated to ensure that reports
  are uploaded to the service even on failures -- by {user}webknjaz.

  GitHub Actions is now configured to also send an explicit notification
  to Codecov about the completion of previously initiated uploads.

  Additionally, the configuration file is now {file}.codecov.yml.

  PRs and issues: {issue}2265

• The linting suite now runs actionlint -- by {user}webknjaz.

  This tool checks typical problems with GitHub Actions workflow
  definitions and has a registry of widely-used GitHub Action
  arguments that it validates.

  PRs and issues: {issue}2266

---

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]

[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 jotak 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.