chore(deps): update pip requirements to v10

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
setuptools-scm	==9.2.2 → ==10.1.2

---

Warning

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

---

Release Notes

pypa/setuptools-scm (setuptools-scm)

v10.1.2: setuptools-scm v10.1.2

Compare Source

Fixed

• Fix DeprecationWarning leak by threading VcsEnvironment through VersionInferenceConfig and using env.make_reader() in _should_write_to_source. (#​1424)

v10.1.1: setuptools-scm v10.1.1

Compare Source

Fixed

• Update CI to use PyPy 3.11 as cryptography has no PyPy 3.10 build available (#​1421)

v10.0.5: setuptools-scm v10.0.5

Compare Source

Fixed

• Allow dump_version() deprecation warning to be silenced by passing scm_version=None. (#​1286)
• Remove [tool.uv.sources] from setuptools-scm/pyproject.toml to fix sdist builds outside the workspace — the workspace root already declares the source mapping for development. (#​1330)

v10.0.4: setuptools-scm v10.0.4

Compare Source

Fixed

• Anchor get_version in setup.py with relative_to and fallback_root so SCM fallbacks (e.g. PKG-INFO) do not resolve against the wrong directory when the build cwd is the workspace or repo root. (#​1302)
• Enter GlobalOverrides for SETUPTOOLS_SCM when using setuptools_scm.get_version / _get_version, avoiding implicit context warnings for direct API callers. (#​1314)

Miscellaneous

• Upgrade pre-commit hooks (Ruff, mypy, codespell), align locked Ruff with hooks, and add Ruff per-file configuration for setuptools_scm re-export modules. (#​1311)

v10.0.3: setuptools-scm v10.0.3

Compare Source

Fixed

• Remove monorepo-only ../vcs-versioning/src from build-system.backend-path so sdists install under PEP 517 (paths must stay inside the source tree). (#​1306)

Miscellaneous

• Add griffecli to test dependencies so the API stability check keeps working after the Griffe CLI was split into a separate package. (#​1310)

v10.0.2: setuptools-scm v10.0.2

Compare Source

Fixed

• Fix version file not generated for editable installs. Version files are now written to the source tree by default during inference (restoring pre-10.x behavior), and also registered as build_py outputs so strict editable installs include them in the persistent auxiliary directory. Set SETUPTOOLS_SCM_WRITE_TO_SOURCE=0 to disable source-tree writing (e.g., for read-only source directories). (#​1298)

v10.0.1: setuptools-scm v10.0.1

Compare Source

Miscellaneous

• Simplify release tag creation to use a single createRelease API call instead of separate createTag/createRef/createRelease calls, avoiding dangling tag objects on partial failures. (#release-pipeline)

---

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.

[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 jpinsonneau for approval. For more information see the Code Review Process.

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

Details

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

[red-hat-konflux]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

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