From patchwork Wed Aug 19 05:22:38 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: auh@yoctoproject.org X-Patchwork-Id: 95640 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 899D0C5DF6D for ; Wed, 19 Aug 2026 05:22:50 +0000 (UTC) Received: from a27-45.smtp-out.us-west-2.amazonses.com (a27-45.smtp-out.us-west-2.amazonses.com [54.240.27.45]) by mx.groups.io with SMTP id smtpd.msgproc01-g2.781.1787116959569681275 for ; Tue, 18 Aug 2026 22:22:39 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@yoctoproject.org header.s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky header.b=SNXzo+lT; dkim=pass header.i=@amazonses.com header.s=hsbnp7p3ensaochzwyq5wwmceodymuwv header.b=Q/HLxtws; spf=pass (domain: us-west-2.amazonses.com, ip: 54.240.27.45, mailfrom: 010101a01878b3bf-eced3564-a8a2-4b71-9a93-bbe139dc401a-000000@us-west-2.amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=lvjh2tk576v2ro5mi6k4dt3mc6wpqbky; d=yoctoproject.org; t=1787116958; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date; bh=N1ZCHUn83FAtkdELCcWPfDgLyvdeHtrlVLMi195R3U4=; b=SNXzo+lTZplQZsVkehkOMZ/BP2ko/nxUPEY5q7mWzNYpJkPMH9XYmbaZA3igOdtr YvKdkuEFJ92YYzqv2CsPnBSp1Lxfzr4iA3ONjTl2U1lJEas66N0j4pLBKFceoi54/hG zQWpZKjMl+fasgXKGClsXOZQjomu0nkCfi2LH8q8= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1787116958; h=Content-Type:MIME-Version:From:To:Cc:Subject:Message-Id:Date:Feedback-ID; bh=N1ZCHUn83FAtkdELCcWPfDgLyvdeHtrlVLMi195R3U4=; b=Q/HLxtws6O7nqvFhLpz7WI6jPrIR8VPhERVJ6T617996zoMEHm2seuwj88VTHX6Q 9isgS4U9VdC5H+JVX9gqXT17t9+nLeLDIaf9drzNY8YEE1zxCs2h9+HrT3Rdf15pmbO hqHAyEiyMi8mkbDI667PMf10qK2oYwrak/Y6Ru2I= MIME-Version: 1.0 From: auh@yoctoproject.org To: Trevor Gamblin Cc: openembedded-core@lists.openembedded.org Subject: [AUH] python3-vcs-versioning: upgrading to 2.3.0 SUCCEEDED Message-ID: <010101a01878b3bf-eced3564-a8a2-4b71-9a93-bbe139dc401a-000000@us-west-2.amazonses.com> Date: Wed, 19 Aug 2026 05:22:38 +0000 Feedback-ID: ::1.us-west-2.9np3MYPs3fEaOBysGKSlUD4KtcmPijcmS9Az2Hwf7iQ=:AmazonSES X-SES-Outgoing: 2026.08.19-54.240.27.45 List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 19 Aug 2026 05:22:50 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/243702 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 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 \