[AUH] python3-setuptools: upgrading to 84.2.0 SUCCEEDED

Hello,

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

Next steps:
    - apply the patch: git am 0001-python3-setuptools-upgrade-84.0.0-84.2.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 536d8728d1a0b2a14b919825264cf424e0c75818 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Tue, 20 Oct 2026 06:44:44 +0000
Subject: [PATCH] python3-setuptools: upgrade 84.0.0 -> 84.2.0

v84.2.0
=======

Features
--------

- Added support for building abi3t extensions and abi3.abi3t wheels on Python
  3.15 and newer. See :pep:`803` and the `Python 3.15 "What's New" entry
  <https://docs.python.org/3.15/whatsnew/3.15.html#pep-803-abi3t-stable-abi-for-
  free-threaded-builds>`_
  for more details.
- Updated vendored packaging version to 26.3, which adds support for the
  ``abi3t`` tag from :pep:`803`.

Bugfixes
--------

- Use target sysconfig data for stable-ABI extension filenames.

v84.1.0
=======

Features
--------

- ``setuptools.archive_util`` now raises the new ``UnsafeMember`` exception when
  an archive member would be extracted outside of the extraction directory,
  where previously such a member was silently skipped. Aborting makes a
  malicious or malformed archive visible to the caller instead of yielding a
  quietly incomplete extraction, and matches the behavior of the standard
  library's ``tarfile`` extraction filters.

Bugfixes
--------

- ``Wheel.install_as_egg`` no longer creates namespace package directories
  outside of the destination egg directory. Entries in a wheel's
  ``namespace_packages.txt`` were split on ``.`` and passed straight to
  ``os.path.join``, so an entry that was absolute, drive-qualified, or UNC
  discarded the destination and placed an ``__init__.py`` at a path chosen by
  the wheel. Namespace entries are now validated as dotted module names on
  every platform -- see GHSA-xmj3-9gf7-h52w.

  This code path is reached only by the deprecated ``setup_requires``
  mechanism when ``setup()`` is invoked outside a PEP 517 frontend; the
  setuptools build backend never reaches it.
- ``setuptools.archive_util`` no longer extracts archive members outside of the
  requested extraction directory. Both the tar and zip formats specify ``/`` as
  the only path separator, but the guard against ``..`` components split member
  names on ``/`` alone, so a name such as ``..\escaped.txt`` was treated as a
  single component and then resolved as a traversal by the filesystem on
  Windows. Member names containing a backslash, a drive letter, or a UNC prefix
  are now rejected on every platform, as are members whose resolved destination
  falls outside the extraction directory -- see GHSA-grgh-hr87-3jpw.

  for deprecated ``python_implementation`` marker.
---
 ...ils-sysconfig.py-make-it-possible-to-substite.patch | 10 +++++-----
 ...tuptools_84.0.0.bb => python3-setuptools_84.2.0.bb} |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)
 rename meta/recipes-devtools/python/{python3-setuptools_84.0.0.bb => python3-setuptools_84.2.0.bb} (94%)