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.3.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-vcs-versioning-upgrade-2.2.4-2.3.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 fd59b0b48bc3e55e54362be15de80be57c32272f Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Wed, 19 Aug 2026 05:15:58 +0000
Subject: [PATCH] python3-vcs-versioning: upgrade 2.2.4 -> 2.3.0
Source: CHANGELOG.md
## 2.3.0 (2026-08-13)
### Added
- Add a ``vcs_versioning.dynamic_metadata`` provider for the
[dynamic-metadata](https://github.com/scikit-build/dynamic-metadata) system.
([#1465](https://github.com/pypa/setuptools-scm/issues/1465))
### Fixed
- Make the `tag.strict` and `scm.git.describe_command` diagnostics actionable
and non-conflicting.
The `tag.strict` future-default notice is now reported by the git backend
rather than at configuration time, and only when the future default would
actually select a different tag for the repository -- the message names both
the current and the future version string. Projects the change cannot affect
are silent, and setting an explicit `describe_command` no longer triggers it at
all, so the two warnings can no longer contradict each other.
The `describe_command` notice is likewise limited to the case where it and an
explicit `tag.strict` really disagree, and no longer claims that `tag.prefix`
has no effect -- prefix stripping applies regardless of how the tag was
selected.
Both are logged at warning level instead of raised as warnings, so
`SETUPTOOLS_SCM_DEBUG=ERROR` silences them.
([#1429](https://github.com/pypa/setuptools-scm/issues/1429))
- Honour `export-ignore` on directories and submodules again in the git file
finder.
The switch from `git archive` to `git ls-files --recurse-submodules` lost two
parts of the archive semantics: `--recurse-submodules` listed every submodule
regardless of `export-ignore`, and the `:(exclude,attr:export-ignore)` pathspec
only matches files, so an `export-ignore` on a directory no longer excluded the
files below it. Projects that kept vendored submodules in an `export-ignore`d
directory suddenly shipped them in their sdists.
The finder now lists a repository without recursion, checks `export-ignore`
for directories via `git check-attr` (which is what `git archive` effectively
does when it skips a tree), and only then descends into the submodules that
survived. Submodule contents are still listed - with their own `.gitattributes`
applied - so `export-ignore` in the parent repository now controls exactly
which submodules get packaged. Submodules that are not checked out are skipped
instead of failing the listing.
([#1469](https://github.com/pypa/setuptools-scm/issues/1469))
- Honour `tag.strict` on Mercurial changesets that carry tags of their own, and
report the coming strict default for Mercurial repositories.
`tag.strict` was only applied when looking for the latest tag, so a
checked-out changeset tagged `event-2024` still produced version `2024` even
with `tag.strict = true`, while git rejected the same tag. Strict matching now
applies to the tags on the changeset too: a changeset carrying only event-style
tags is treated as untagged and versioning continues from the last real version
tag, matching `git describe --match`. When several tags sit on one changeset,
the version-shaped one is now selected instead of whichever Mercurial h
[Changelog truncated as it exceeds 3000 characters;
the full changelog can be found in an attachment to the AUH email]
---
...-vcs-versioning_2.2.4.bb => python3-vcs-versioning_2.3.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-vcs-versioning_2.2.4.bb =>
python3-vcs-versioning_2.3.0.bb} (91%)
diff --git a/meta/recipes-devtools/python/python3-vcs-versioning_2.2.4.bb
b/meta/recipes-devtools/python/python3-vcs-versioning_2.3.0.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-vcs-versioning_2.2.4.bb
rename to meta/recipes-devtools/python/python3-vcs-versioning_2.3.0.bb
index c8665d90c9..aae305d144 100644
--- a/meta/recipes-devtools/python/python3-vcs-versioning_2.2.4.bb
+++ b/meta/recipes-devtools/python/python3-vcs-versioning_2.3.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] =
"ed718fdee42170e128a8add6f23f53aa64dc7d9ab2de87d3083a691df881a809"
+SRC_URI[sha256sum] =
"eb7f5aa2ff5d0c9f8c108ec0bb9476e2ddbe708f08a5e41df4c7977062484cf7"
SRC_URI += "\
file://run-ptest \
--
2.47.1
packages/x86-64-v3-poky-linux/python3-vcs-versioning: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning: SRC_URI changed from "https://files.pythonhosted.org/packages/source/v/vcs_versioning/vcs_versioning-2.2.4.tar.gz;downloadfilename=vcs_versioning-2.2.4.tar.gz file://run-ptest" to "https://files.pythonhosted.org/packages/source/v/vcs_versioning/vcs_versioning-2.3.0.tar.gz;downloadfilename=vcs_versioning-2.3.0.tar.gz file://run-ptest" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dbg: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dbg: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dev: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-dev: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-doc: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-doc: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-locale: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-locale: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: FILELIST: added "/usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_tag_strict_diagnostics.py /usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_hg_tag_strict.py /usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_dynamic_metadata.py" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: PKGSIZE changed from 248397 to 271248 (+9%) packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-src: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-src: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-staticdev: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-staticdev: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: FILELIST: directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info -> /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info, directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info/licenses -> /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info/licenses, added "/usr/lib/python3.14/site-packages/vcs_versioning/_dynamic_metadata.py /usr/lib/python3.14/site-packages/vcs_versioning/__pycache__/_dynamic_metadata.cpython-314.pyc" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PV changed from "2.2.4" to "2.3.0" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PKGV changed from 2.2.4 [default] to 2.3.0 [default] packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: PKGSIZE changed from 735834 to 773736 (+5%) Changes to packages/x86-64-v3-poky-linux/python3-vcs-versioning (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info /usr/lib/python3.14/site-packages/vcs_versioning/_dynamic_metadata.py was added /usr/lib/python3.14/site-packages/vcs_versioning/__pycache__/_dynamic_metadata.cpython-314.pyc was added Changes to packages/x86_64-linux/python3-vcs-versioning-native (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info /usr/lib/python3.14/site-packages/vcs_versioning/_dynamic_metadata.py was added /usr/lib/python3.14/site-packages/vcs_versioning/__pycache__/_dynamic_metadata.cpython-314.pyc was added
packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning-ptest: FILELIST: added "/usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_hg_tag_strict.py /usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_dynamic_metadata.py /usr/lib/python3-vcs-versioning/ptest/testing_vcs/test_tag_strict_diagnostics.py" packages/x86-64-v3-poky-linux/python3-vcs-versioning/python3-vcs-versioning: FILELIST: directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info/licenses -> /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info/licenses, directory renamed /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info -> /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info, added "/usr/lib/python3.14/site-packages/vcs_versioning/_dynamic_metadata.py /usr/lib/python3.14/site-packages/vcs_versioning/__pycache__/_dynamic_metadata.cpython-314.pyc" Changes to packages/x86-64-v3-poky-linux/python3-vcs-versioning (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info /usr/lib/python3.14/site-packages/vcs_versioning/_dynamic_metadata.py was added /usr/lib/python3.14/site-packages/vcs_versioning/__pycache__/_dynamic_metadata.cpython-314.pyc was added Changes to packages/x86_64-linux/python3-vcs-versioning-native (sysroot): /usr/lib/python3.14/site-packages/vcs_versioning-2.2.4.dist-info moved to /usr/lib/python3.14/site-packages/vcs_versioning-2.3.0.dist-info /usr/lib/python3.14/site-packages/vcs_versioning/_dynamic_metadata.py was added /usr/lib/python3.14/site-packages/vcs_versioning/__pycache__/_dynamic_metadata.cpython-314.pyc was added
Changelog for python3-vcs-versioning: 2.2.4 -> 2.3.0 Source: CHANGELOG.md ## 2.3.0 (2026-08-13) ### Added - Add a ``vcs_versioning.dynamic_metadata`` provider for the [dynamic-metadata](https://github.com/scikit-build/dynamic-metadata) system. ([#1465](https://github.com/pypa/setuptools-scm/issues/1465)) ### Fixed - Make the `tag.strict` and `scm.git.describe_command` diagnostics actionable and non-conflicting. The `tag.strict` future-default notice is now reported by the git backend rather than at configuration time, and only when the future default would actually select a different tag for the repository -- the message names both the current and the future version string. Projects the change cannot affect are silent, and setting an explicit `describe_command` no longer triggers it at all, so the two warnings can no longer contradict each other. The `describe_command` notice is likewise limited to the case where it and an explicit `tag.strict` really disagree, and no longer claims that `tag.prefix` has no effect -- prefix stripping applies regardless of how the tag was selected. Both are logged at warning level instead of raised as warnings, so `SETUPTOOLS_SCM_DEBUG=ERROR` silences them. ([#1429](https://github.com/pypa/setuptools-scm/issues/1429)) - Honour `export-ignore` on directories and submodules again in the git file finder. The switch from `git archive` to `git ls-files --recurse-submodules` lost two parts of the archive semantics: `--recurse-submodules` listed every submodule regardless of `export-ignore`, and the `:(exclude,attr:export-ignore)` pathspec only matches files, so an `export-ignore` on a directory no longer excluded the files below it. Projects that kept vendored submodules in an `export-ignore`d directory suddenly shipped them in their sdists. The finder now lists a repository without recursion, checks `export-ignore` for directories via `git check-attr` (which is what `git archive` effectively does when it skips a tree), and only then descends into the submodules that survived. Submodule contents are still listed - with their own `.gitattributes` applied - so `export-ignore` in the parent repository now controls exactly which submodules get packaged. Submodules that are not checked out are skipped instead of failing the listing. ([#1469](https://github.com/pypa/setuptools-scm/issues/1469)) - Honour `tag.strict` on Mercurial changesets that carry tags of their own, and report the coming strict default for Mercurial repositories. `tag.strict` was only applied when looking for the latest tag, so a checked-out changeset tagged `event-2024` still produced version `2024` even with `tag.strict = true`, while git rejected the same tag. Strict matching now applies to the tags on the changeset too: a changeset carrying only event-style tags is treated as untagged and versioning continues from the last real version tag, matching `git describe --match`. When several tags sit on one changeset, the version-shaped one is now selected instead of whichever Mercurial happened to list first. The `tag.strict` divergence diagnostic added in #1429 now covers Mercurial as well, naming the current and future version whenever the coming default would change them. Both backends share the message, and the git-only helpers moved to `_backends/_scm_workdir.py`. Note that the Mercurial backend required a dot in version tags before setuptools-scm 9, so for Mercurial projects the coming strict default restores the historical behavior. ([#1495](https://github.com/pypa/setuptools-scm/issues/1495))
0001-python3-vcs-versioning-upgrade-2.2.4-2.3.0.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#243702): https://lists.openembedded.org/g/openembedded-core/message/243702 Mute This Topic: https://lists.openembedded.org/mt/120825678/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
