[AUH] python3-pyproject-hooks: upgrading to 1.3.3 SUCCEEDED

Hello,

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

Next steps:
    - apply the patch: git am 0001-python3-pyproject-hooks-upgrade-1.2.0-1.3.3.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 02a620366f5d0dabcd8d83c2a43141bedbe23134 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Thu, 17 Sep 2026 06:13:36 +0000
Subject: [PATCH] python3-pyproject-hooks: upgrade 1.2.0 -> 1.3.3

Source: docs/changelog.rst

v1.3.3
------

- No code changes from 1.3. The git tags and the version number got out of sync
  while fixing an issue with the Github actions workflow to publish the release.
  1.3.3 exists only to get them back in sync without reassigning any tags.

v1.3
----

- Python 3.8 or above is now required (:pr:`214`).
- UserWarnings from the backend are now captured and re-emitted in the frontend
  process as a new category ``BuildBackendWarning``, so that frontends can
  control how they are shown to users (:pr:`213`).
- Show the traceback from the backend on a ``BackendUnavailable`` error (:pr:`219`).
- Fix the return type annotation for ``prepare_metadata_for_build_wheel``
  (:pr:`209`).
- Fix removing the internal ``_in_process`` directory from ``sys.path`` where
  the install location includes a symlink (:pr:`230`).
- Use ``os.path.commonpath`` instead of the deprecated ``commonprefix`` to
  validate the location of in-tree backends.
- Fix in-tree backends in locations containing the path separator character -
  ``:`` on Posix platforms, ``;`` on Windows (:pr:`232`).
- Fix finding distribution metadata with ``importlib.metadata`` in the backend
  when an in-tree backend is used (:pr:`212`).
- ``pyproject_hooks`` can be built from source using flit_core 4.x (:pr:`233`).
- Document that the ``hooks.subprocess_runner`` context manager API is not
  thread-safe (:pr:227`)

  in setuptools compatibility in 1.1 (PR :pr:`199`).
  before imporing the backend (PR :pr:`193`).
- Rely on preferred "files" API on Python 3.9 and later (:issue:`140`).
---
 ...yproject-hooks_1.2.0.bb => python3-pyproject-hooks_1.3.3.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-pyproject-hooks_1.2.0.bb => python3-pyproject-hooks_1.3.3.bb} (86%)