Update setuptools-scm requirement from >=8 to >=9.2.2

[dependabot]

Updates the requirements on setuptools-scm to permit the latest version.

Changelog

Sourced from setuptools-scm's changelog.

v9.2.2

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

Fixed

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

v9.2.0

Added

• add simplified activation via setuptools-scm[simple] extra

  A new streamlined way to enable version inference without requiring a [tool.setuptools_scm] section. When setuptools-scm[simple] is in build-system.requires and version is in project.dynamic, version inference is automatically enabled with default settings.

Removed

• unchecked simplified activation - too many projects use setups where it would fail

Changed

• refine activation logic and add unittest for the relevant cases instead of trying to speedrun setuptools

v9.1.1 (yanked)

Fixed

• fix #1194: correctly handle version keyword when pyproject metadata is missing

v9.1.0 (yanked)

Fixed

• complete reiteration of the decision logic for enabling version inference on setuptools_scm

... (truncated)

Commits

• e56b78f Merge pull request #1232 from RonnyPfannschmidt/fix-1231-dont-warn-when-no-guess
• 4f55e95 docs: update changelog for v9.2.2 patch release
• 95a0c47 fix: don't warn about tool.setuptools.dynamic.version when only using file fi...
• 338f562 Merge pull request #1226 from RonnyPfannschmidt/prepare-release
• a893634 Prepare release v9.2.1
• ad83282 Merge pull request #1225 from pypa/pre-commit-ci-update-config
• 20a4464 [pre-commit.ci] pre-commit autoupdate
• 70f6942 Merge pull request #1219 from RonnyPfannschmidt/fix-1216-explicitly-deprecate...
• 14d85c0 Install Mercurial on Windows runners via Chocolatey
• 8c5cec9 Fix API stability check workflow to install griffe and improve reporting
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[rtibblesbot]

setuptools-scm >=8 → >=9.2.2 — major lower-bound bump, build-system only, CI passing.

Semver risk: major (crosses v8→v9). Dependency type: [build-system].requires — not installed at runtime, no production exposure.

Changelog highlights across the range:

• v9.0.0: git_describe_command migrated to new scm config — morango sets this key; CI passing confirms it is still honoured.
• v9.0.0: Commit ID added to default version file template — affects the auto-generated morango/_version.py (untracked), no functional impact.
• v9.0.0: Python version build-tag fix — not applicable; morango uses tag-based versioning with no such suffixes.
• v9.2.0: New [simple] extra — opt-in, no effect on existing configs.
• v9.2.1/v9.2.2: Bugfixes only.
• Security fixes: none. Peer-dependency changes: none.

Yanked versions: v9.0.0, v9.1.0, v9.1.1 were yanked for regressions. Dependabot correctly floors at >=9.2.2, the first stable v9 release.

Open ceiling (>=9.2.2) admits v10.x, which exists — pre-existing policy, unchanged by this PR.

CI passing is the meaningful signal here; it validates the git_describe_command config and version file generation against v9.x. No code changes required.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a dependency-update review pipeline over the version bump:

• Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
• Extracted the changelog and release notes across the version range
• Assessed compatibility with this project's usage and whether any code changes are required
• Treated CI as the primary safety net
• Scaled the review depth to the update's risk
• Chose the verdict from semver risk, changelog findings, and CI status