Update dependency setuptools-scm to >=10.3.2

[olehermanse]

This PR contains the following updates:

Package	Change	Age	Confidence
setuptools-scm	>=10.2.3 → >=10.3.2

---

Release Notes

pypa/setuptools-scm (setuptools-scm)

v10.3.2: setuptools-scm v10.3.2

Compare Source

Fixed

• Stop the command mixins from reordering a project's own build_py, egg_info
  or bdist_wheel MRO. ScmVersionFileMixin and friends inherited from the
  corresponding setuptools command, so wrapping a project class built on a disjoint
  hierarchy -- distutils.command.build_py, or the standalone wheel package's
  bdist_wheel -- placed setuptools' command ahead of the project's class.
  setuptools.build_py.run() does not delegate any further, so the project's
  run() was silently skipped, surfacing as
  error: package directory '...' does not exist. The mixins now carry no runtime
  base class and linearise to (wrapped, mixin, *project_command.__mro__). (#​1531)

• Leave a project's cmdclass alone when setuptools-scm is installed but not
  actually inferring a version. build_py, egg_info and bdist_wheel are
  now registered only once version inference has stored data on the distribution --
  the precondition for any of the mixins doing something. Previously every project
  with a pyproject.toml had its commands wrapped, including projects with no
  [tool.setuptools_scm] section at all.

  Note for projects that used to configure setuptools-scm and no longer do: a
  scm_version.json left behind in a stale *.egg-info directory is no longer
  stripped from built wheels, because the bdist_wheel mixin that strips it is no
  longer registered either. Remove the stale *.egg-info directory. (#​1533)

v10.3.1: setuptools-scm v10.3.1

Compare Source

Fixed

• Require vcs-versioning>=2.4.0. setuptools-scm 10.3.0 declared >=2.3.2 but
  imports vcs_versioning._file_finders.scm_search_known_failed, which vcs-versioning
  only gained in 2.4.0, so installing it alongside an older vcs-versioning failed with
  ImportError. CI now installs setuptools-scm against the oldest vcs-versioning its
  metadata permits, so the lower bound can no longer go stale unnoticed. (#​1528)

v10.3.0: setuptools-scm v10.3.0

Compare Source

Deprecated

• Emit a DeprecationWarning when the setuptools.file_finders entry point is invoked for a project that does not configure setuptools-scm. The entry point will be removed in a future major release. (#​1407)

Fixed

• Run the setuptools.file_finders hook inside a setuptools-scm override context. It previously resolved settings under the VCS_VERSIONING prefix only, so documented variables such as SETUPTOOLS_SCM_SUBPROCESS_TIMEOUT and SETUPTOOLS_SCM_HG_COMMAND were ignored when finding files.

  When version inference has already run and found no SCM checkout, the egg_info mixin now tells the file finders so, rather than letting walk_revctrl() re-probe every backend for a repository known to be absent. (#​1212)

---

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

---

This PR has been generated by Mend Renovate CLI.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.31%. Comparing base (7e4fdde) to head (f90cec7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #235   +/-   ##
=======================================
  Coverage   52.31%   52.31%           
=======================================
  Files          32       32           
  Lines        4110     4110           
=======================================
  Hits         2150     2150           
  Misses       1960     1960           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.