similarity index 91%
rename from meta/recipes-devtools/python/python3-vcs-versioning_2.3.4.bb
rename to meta/recipes-devtools/python/python3-vcs-versioning_2.4.0.bb
@@ -5,7 +5,7 @@ library that can be used independently of setuptools."
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=c9b06ad2ebd7e2e82d34b3caf353e7d5"
-SRC_URI[sha256sum] = "f3443da15a34a32755b04324e33c6166add300c7661f45902225190c9337f711"
+SRC_URI[sha256sum] = "cc4b66c02ae4cfb51e843910024f7142464c3391bb1f7e04608578b45046891b"
SRC_URI += "\
file://run-ptest \
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *python3-vcs-versioning* to *2.4.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-vcs-versioning-upgrade-2.3.4-2.4.0.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 8e9c7b4238086925e620dd5574e93fa943ef2066 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Mon, 14 Sep 2026 05:26:43 +0000 Subject: [PATCH] python3-vcs-versioning: upgrade 2.3.4 -> 2.4.0 Source: CHANGELOG.md ## 2.4.0 (2026-09-12) ### Added - Add `scm.git.distance_scope` and `scm.git.distance_count`, restricting the distance count to the commits that touch a monorepo project (and optionally further shared directories) instead of every commit in the repository. Counting uses `--full-history` by default, or `--first-parent`; git's default history simplification is not offered because it can make the distance shrink across a merge. Git only. ([#1056](https://github.com/pypa/setuptools-scm/issues/1056)) ### Fixed - Select file finders by the VCS marker their entry point is named for (`.git`, `.hg`, `.jj`) instead of running every backend's command in turn. A tree with no VCS marker -- an unpacked sdist, say -- now spawns no subprocess at all, so a slow `hg` on `PATH` can no longer fail an unrelated build. The finders also survive a subprocess timeout: `subprocess.TimeoutExpired` was uncaught and aborted the build, and is now treated like any other failed probe. ([#1212](https://github.com/pypa/setuptools-scm/issues/1212)) - Prefer the fallback metadata nearest the project directory. A `.git_archival.txt` or `PKG-INFO` at the VCS root no longer shadows a monorepo project's own, which silently produced the root project's version. ([#1522](https://github.com/pypa/setuptools-scm/issues/1522)) --- ...-vcs-versioning_2.3.4.bb => python3-vcs-versioning_2.4.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/python/{python3-vcs-versioning_2.3.4.bb => python3-vcs-versioning_2.4.0.bb} (91%)