similarity index 91%
rename from meta/recipes-devtools/python/python3-vcs-versioning_2.3.1.bb
rename to meta/recipes-devtools/python/python3-vcs-versioning_2.3.2.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] = "806635bd0ea653c96af98a70624be758d408a989f2cd0b390e63474d99f96b63"
+SRC_URI[sha256sum] = "24abddff97aecf44cf3fec727eae8d76d9c6f70f5acb39afc41f824d69f2aac5"
SRC_URI += "\
file://run-ptest \
Changelog: - Fixed - Register the `pkginfo` workdir discovery factory in vcs-versioning itself. `PKG-INFO` is standard sdist metadata, not a setuptools artifact, but its factory was only registered by setuptools-scm -- so a standalone vcs-versioning install could not infer a version from an sdist. This broke sdist builds for non-setuptools backends, e.g. meson-python calling `python -m vcs_versioning` from `project()`. - Fallback workdir candidates are now ordered by how much metadata they carry (egg-info, then archival, then `PKG-INFO`) instead of by entry point iteration order, so a setuptools built sdist keeps using its `scm_version.json` now that the two factories ship from different distributions. - Miscellaneous - Stop shipping a per-package `uv.lock` in the sdist. It could not be generated correctly whenever `setuptools-scm` required an unreleased `vcs-versioning`, which broke the release proposal workflow. Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> --- ...{python3-vcs-versioning_2.3.1.bb => python3-vcs-versioning_2.3.2.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)