Sourced from setuptools-scm's changelog.

v6.0.1

• fix #537: drop node_date on old git to avoid errors on missing %cI

v6.0.0

• fix #517: drop dead python support >3.6 required
• drop dead setuptools support > 45 required (can install wheels)
• drop egg building (use wheels)
• add git node_date metadata to get the commit time-stamp of HEAD
• allow version schemes to be priority ordered lists of version schemes
• support for calendar versioning (calver) by date

v5.0.2

• fix #415: use git for matching prefixes to support the windows situation

v5.0.1

• fix #509: support SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${DISTRIBUTION_NAME} for pyproject.toml

v5.0.0

Breaking changes:

• fix #339: strict errors on missing scms when parsing a scm dir to avoid false version lookups
• fix #337: if relative_to is a directory instead of a file, consider it as direct target instead of the containing folder and print a warning

Bugfixes:

• fix #352: add support for generally ignoring specific vcs roots
• fix #471: better error for version bump failing on complex but accepted tag
• fix #479: raise indicative error when tags carry non-parsable information
• Add no-guess-dev which does no next version guessing, just adds .post1.devN in case there are new commits after the tag
• add python3.9
• enhance documentation
• consider SOURCE_DATE_EPOCH for versioning
• add a version_tuple to write_to templates
• fix #321: add support for the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${DISTRIBUTION_NAME} env var to target the pretend key
• fix #142: clearly list supported scm
• fix #213: better error message for non-zero dev numbers in tags
• fix #356: add git branch to version on describe failure

v4.1.2

... (truncated)

• abb67b1 Merge pull request #538 from RonnyPfannschmidt/fix-537-drop-node-date-on-old-git
• 32ab7e6 drop node_date on old git
• 53c16ce also require setuptools >45 in pyproject.toml
• 8fe78fe drop missed eggs
• 39ad2b6 main branch
• df8ba7e finalize changelog
• 90931fd Merge pull request #533 from henryiii/patch-1
• c429495 Merge pull request #534 from henryiii/patch-2
• 3112db8 Merge pull request #529 from ikerreyes/calver-by-date
• f0be71f fix: drop more Python 2 manually
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)