[AUH] python3-pyproject-metadata: upgrading to 0.12.1 SUCCEEDED

Hello,

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

Next steps:
    - apply the patch: git am 0001-python3-pyproject-metadata-upgrade-0.11.0-0.12.1.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 4855fd9e30458a3a6fe275374bd95436a0909e90 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Tue, 4 Aug 2026 06:01:34 +0000
Subject: [PATCH] python3-pyproject-metadata: upgrade 0.11.0 -> 0.12.1

Source: docs/changelog.md

## 0.12.1 (7-3-2026)

Fixes:

- Collect a config error instead of raising a raw `TypeError` when
  `project.dynamic` contains a non-string (unhashable) entry with
  `all_errors=True`.

## 0.12.0 (7-3-2026)

Features:

- Support [PEP 808](https://peps.python.org/pep-0808/) (partially dynamic
  project metadata) (METADATA 2.6).
- Add support for Python 3.15.
- Warn ([PEP 685](https://peps.python.org/pep-0685/)) when an extra name in
  `project.optional-dependencies` is not a valid name. The extra is still
  emitted, only a `ConfigurationWarning` is produced.

Fixes:

- Error on an unset dynamic version instead of silently writing
  `Version: 0.0.0`. If `"version"` is declared in `project.dynamic` but never
  assigned by the build backend, writing the metadata now raises a
  `ConfigurationError` (`Field "project.version" missing`), restoring the 0.8.x
  behavior that regressed in the 0.9 rewrite.
- Don't crash on a non-table `[project]` when `all_errors=True`.
- Tighten `license-files` glob checks and private-tag parsing.
- Handle braces in user data within error messages.
- Correct the `Import-Namespace` field name in the metadata mapping.
- Fix UTF-8 author and maintainer names.

Performance:

- Cache `get_type_hints` and precompile dispatch patterns.

Documentation:

- Fix a stale dynamic docstring and a broken module example.
- Add a documentation project URL.

Internal and CI:

- Refactoring: consistent dataclass decorators, sorted constant entries, and
  removal of duplicate imports and dead code.
- Cover defensive branches in dispatch helpers and validators.
- Secure GitHub Actions workflows and bump pinned/downstream dependencies.
---
 ...-metadata_0.11.0.bb => python3-pyproject-metadata_0.12.1.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-pyproject-metadata_0.11.0.bb => python3-pyproject-metadata_0.12.1.bb} (89%)