Hi,
I took a quick look at the generated changelog and I have identified the 
problem.

Problem:
AUH Updates from 1.5.1 to 1.6.0 but there is no 1.5.1 information in the 1.6.0 
changelog.rst, but it is in the old version.

1.6.0 CHANGELOG.rst
grep "(2026"  CHANGELOG.rst
 1.6.0 (2026-08-27)
 1.5.0 (2026-04-30)
 1.4.4 (2026-04-22)
 1.4.3 (2026-04-10)
 1.4.2 (2026-03-25)
 1.4.1 (2026-03-24)
 1.4.0 (2026-01-08)

1.5.1 CHANGELOG.rst
git show main:CHANGELOG.rst | grep "(2026"
 1.5.1 (2026-07-09)
 1.5.0 (2026-04-30)
 1.4.4 (2026-04-22)
 1.4.3 (2026-04-10)
 1.4.2 (2026-03-25)
 1.4.1 (2026-03-24)
 1.4.0 (2026-01-08)

Then the changelog diff generated is broken since it mixes content from 1.5.1 
and 1.6.0.

I'll look into adding a guard for it. The quick workaround is to just manually 
the relevant section of new CHANGELOG.rst into the commit message

Best regards,
Daniel


________________________________________
From: [email protected] 
<[email protected]> on behalf of Auto Upgrade Helper via 
lists.openembedded.org <[email protected]>
Sent: Friday, August 28, 2026 7:57 AM
To: Ross Burton
Cc: [email protected]
Subject: [OE-core] [AUH] python3-build: upgrading to 1.6.0 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *python3-build* to *1.6.0* 
has Succeeded.

Next steps:
    - apply the patch: git am 0001-python3-build-upgrade-1.5.1-1.6.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 7b21d98057ce518b5e3cf7f2f7cff239e7c95da7 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Fri, 28 Aug 2026 05:36:35 +0000
Subject: [PATCH] python3-build: upgrade 1.5.1 -> 1.6.0

Source: CHANGELOG.rst

1.6.0 (2026-08-27)
- Pass ``--dependency-constraints-txt`` files through to the installer 
unmodified instead of re-parsing them into a
  deduplicated set of lines, fixing a case where a hashed requirement (e.g. 
from ``pip-compile --generate-hashes``) could
  have its ``--hash`` continuation line separated from its requirement line and 
silently dropped, depending on the
  interpreter's hash seed - by :user:`manfred-kaiser` (:issue:`1140`)
**********
 Removals
**********

- Remove ``exc_info`` parameter and attribute from ``BuildBackendException``. - 
by :user:`layday` (:issue:`1161`)

**************
 Deprecations
**************
- :issue:`1058`, :issue:`1060`, :issue:`1062`, :issue:`1093`, :issue:`1099`, 
:issue:`1107`, :issue:`1113`, :issue:`1117`, :issue:`1122`, :issue:`1124`, 
:issue:`1128`, :issue:`1132`
---
 .../python3-build/check-valid-dist.patch       | 18 ++++++++++++------
 ...3-build_1.5.1.bb => python3-build_1.6.0.bb} |  2 +-
 2 files changed, 13 insertions(+), 7 deletions(-)
 rename meta/recipes-devtools/python/{python3-build_1.5.1.bb => 
python3-build_1.6.0.bb} (87%)

diff --git a/meta/recipes-devtools/python/python3-build/check-valid-dist.patch 
b/meta/recipes-devtools/python/python3-build/check-valid-dist.patch
index dd6f256e26..82c31a49a4 100644
--- a/meta/recipes-devtools/python/python3-build/check-valid-dist.patch
+++ b/meta/recipes-devtools/python/python3-build/check-valid-dist.patch
@@ -1,4 +1,7 @@
-Ignore invalid distributions when checking dependencies
+From a2a217409e01e3ebea88dce85d81dbe6b3c79187 Mon Sep 17 00:00:00 2001
+From: Ross Burton <[email protected]>
+Date: Wed, 12 Aug 2026 12:35:29 +0100
+Subject: [PATCH] Ignore invalid distributions when checking dependencies

 If there's an empty directory foo-1.2.dist-info/ on the search path then
 importlib will return that as a distribution called "foo".
@@ -12,12 +15,15 @@ the dist-info directory is empties but remains in the 
sysroot.

 Upstream-Status: Submitted [https://github.com/pypa/build/pull/1145]
 Signed-off-by: Ross Burton <[email protected]>
+---
+ src/build/_util.py | 5 +++++
+ 1 file changed, 5 insertions(+)

-diff --git i/src/build/_util.py w/src/build/_util.py
-index c365003..ba047c7 100644
---- i/src/build/_util.py
-+++ w/src/build/_util.py
-@@ -67,6 +67,11 @@ def _check_dependency(
+diff --git a/src/build/_util.py b/src/build/_util.py
+index cce8f94..54bc02c 100644
+--- a/src/build/_util.py
++++ b/src/build/_util.py
+@@ -63,6 +63,11 @@ def _check_dependency(
          yield (*ancestral_req_strings, normalised_req_string)
          return

diff --git a/meta/recipes-devtools/python/python3-build_1.5.1.bb 
b/meta/recipes-devtools/python/python3-build_1.6.0.bb
similarity index 87%
rename from meta/recipes-devtools/python/python3-build_1.5.1.bb
rename to meta/recipes-devtools/python/python3-build_1.6.0.bb
index d572ca846f..acec9cd9ef 100644
--- a/meta/recipes-devtools/python/python3-build_1.5.1.bb
+++ b/meta/recipes-devtools/python/python3-build_1.6.0.bb
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=310439af287b0fb4780b2ad6907c256c"

 SRC_URI += "file://check-valid-dist.patch"

-SRC_URI[sha256sum] = 
"94e17f1db803ab22f46049376c44c8437c52090f0dfdf1adc43df56542d644fb"
+SRC_URI[sha256sum] = 
"bd2c8afc603e7a2e0ce70e2ea85f0a6d02043bafbd307f5bada0f98669eca5af"

 inherit pypi python_flit_core

--
2.47.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#244829): 
https://lists.openembedded.org/g/openembedded-core/message/244829
Mute This Topic: https://lists.openembedded.org/mt/120968616/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to