devel/py-vcs-versioning 2.3.4 NetBSD

2.6.0 (2026-10-06) Added - Add the `towncrier-fragments-zerover` version scheme: like `towncrier-fragments`, but while the last tag is `0.x`, `breaking` and `removal` fragments bump the minor version and only a `major` fragment proposes `1.0.0`.

## 2.5.0 (2026-09-23) ### Added - Add `discover_file_workdir()`, which finds the checkout a project sits in for the purpose of listing files. `discover_workdir()` answers which checkout defines the version, scoped by `root` and `search_parent_directories`; which files a project ships is a separate question, and a project in a subdirectory of a checkout still ships that checkout's files. ([#1543](https://github.com/pypa/setuptools-scm/issues/1543)) ### Fixed - Accept the `tool` keyword in `_version_missing()` again. setuptools-scm 10.1.0 through 10.2.3 pass it and allow any `vcs-versioning<3`; since 2.4.1 removed it, a build without a detectable version failed with `TypeError: _version_missing() got an unexpected keyword argument 'tool'` …

2.4.1 (2026-09-16) Fixed - The error raised when a `.jj/` directory is found but `jj` is not installed now names the environment variables that actually disable jj discovery (`SETUPTOOLS_SCM_DISABLE_JJ=1` / `VCS_VERSIONING_DISABLE_JJ=1`) instead of an unprefixed `DISABLE_JJ=1`, which was never read. - The "unable to detect version" error now names the environment variables the running integration actually reads. It previously suggested `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME}` unconditionally, which is not read by `vcs-versioning` on its own (or by any other integrator), and it named setuptools-scm as the failing tool regardless of which one ran. When the distribution name is known the suggested variable is spelled out in …

2.3.4 (2026-09-03) Fixed - Ensure the vcs-versioning testsuite passes without setuptools-scm installed; the egg-info vs PKG-INFO discovery priority test moved to the setuptools-scm testsuite, which owns the egg-info entry point it needs. 2.3.3 (2026-09-03) Fixed - The `semver-pep440` and `semver-pep440-release-branch` version schemes now keep the PEP 440 epoch of the tag they are derived from, instead of emitting a version that sorts below it.