[AUH] python3-numpy: upgrading to 2.5.4 SUCCEEDED

Hello,

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

Next steps:
    - apply the patch: git am 0001-python3-numpy-upgrade-2.5.3-2.5.4.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 51bae7cbe369a9f6a105f12218df181d6dbba9fa Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Sun, 11 Oct 2026 05:17:42 +0000
Subject: [PATCH] python3-numpy: upgrade 2.5.3 -> 2.5.4

Contributors
============

A total of 9 people contributed to this release.  People with a "+" by their
names contributed a patch for the first time.

Pull requests merged
====================

A total of 17 pull requests were merged for this release.
.. currentmodule:: numpy

=========================
NumPy 2.5.4 Release Notes
=========================

*Released on 2026-10-10.*

NumPy 2.5.4 is a patch release that fixes bugs discovered after the 2.5.3
release. Highlights are:

- Many typing fixes and improvements,
- A workaround for the MSVC 19.51 bug, see below.

This release supports Python versions 3.12-3.15.

Improvements
============

- ``numpy.linalg.svd`` and ``numpy.linalg.lstsq`` now raise for inputs
  containing
  infinities instead of returning garbage results.
- Fixed hangs in ``numpy.linalg.svd`` and ``numpy.linalg.lstsq`` for certain
  inputs
  containing infinities for recent versions of some LAPACK implementations.
- ``numpy.linalg.cond`` now handles non-finite inputs more consistently.

  (`gh-32593 < >`__)

StringDType hashing with NaN sentinels
--------------------------------------
``StringDType`` instances with equivalent floating-point NaN sentinels now
have equal hashes. Previously, distinct NaN objects could produce equal
dtype instances with different hashes, causing dictionary lookups and set
deduplication to fail.

(`gh-32563 < >`__)

Changes
=======

``MaskedArray`` resets a fill_value that cannot be represented in a new dtype
-----------------------------------------------------------------------------
A fill_value copied from a source array is now reset to the default fill_value
for the new dtype when it cannot be represented in that dtype.  Previously the
copied value could be stale: ufuncs that change dtype left the result holding a
fill_value typed for the old dtype, which raised a ``TypeError`` only when
something later validated it (such as ``.view()``), and a floating point
fill_value that overflows an integer dtype was kept as an out-of-range value
together with a ``RuntimeWarning``.  Both now fall back to the default,
including when a masked array is passed to ``MaskedArray`` with a different
``dtype``.  A fill_value given explicitly by the user is still validated and
raises as before.  This can now raise a ``ComplexWarning`` if the fill_value is
complex and the new dtype is real.

(`gh-32508 < >`__)
(`gh-32562 < >`__)

Contributors
============

A total of 9 people contributed to this release.  People with a "+" by their
names contributed a patch for the first time.

Pull requests merged
====================

A total of 17 pull requests were merged for this release.

---
title: Release 1.11.0
short-description: Release notes for 1.11.0
# New features

Meson 1.11.0 was released on 13 April 2026
## BuildTarget(install_dir) length > 1 replaced with keywords

Build targets previously supported (with limited documentation) passing an array
of more than one element to `install_dir:` (except in some wrappers), and
would map these additional `install_dir`s to extra outputs. This was only used
by
Vala, and separate explicit keyword arguments are now available that provide
the same functionality.

Code like this:
```meson
library(
  'foo',
  'foo.vala',
  install : true,
  install_dir : [true, get_option('includedir') / 'foo', true],
)
```

should now be written as the much clearer:

```meson
library(
  'foo',
  'foo.vala',
  install : true,
  install_vala_header : get_option('includedir') / 'foo',
  install_vala_vapi : true,
)
```

Note that the default is `false` for the Vala extra outputs.
## Cargo workspace object

Meson is now able to parse the toplevel `Cargo.toml` file of the
project when the `workspace()` method of the Rust module is called.
This guarantees that features are resolved according to what is
in the `Cargo.toml` file, and in fact enables configuration of
features for the build.

The returned object allows retrieving features and dependencies
for Cargo subprojects, and contains methods to build targets
declared in `Cargo.toml` files.

While Cargo subprojects remain experimental, the Meson project will
try to keep the workspace object reasonably backwards-compatible.

## Cython no longer requires explicitly enabling C or C++

This only provides these languages as an implementation detail of Cython, so
native C/C++ targets cannot be compiled.

## Deduplication of OpenMP linker arguments
Meson now deduplicates linker arguments `-fopenmp` and `-qopenmp`.
## `meson dist` now accepts `-j`/`--num-processes`

`meson dist` now supports a `-j`/`--num-processes` flag to control the number of
parallel processes used during the distribution check (compilation and testing
of
the generated package).  The `MESON_NUM_PROCESSES` environment variable is also
honored, consistent with other Meson commands.

## Deprecate `should_fail` and rename it to `expected_fail`, also introduce
`expected_exitcode`

In 1.11.0 `should_fail` has been renamed to `expected_fail`.

Before 1.11.0,

[Changelog truncated as it exceeds 5000 characters;
the full changelog can be found in an attachment to the AUH email]
---
 .../python/{python3-numpy_2.5.3.bb => python3-numpy_2.5.4.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/python/{python3-numpy_2.5.3.bb => python3-numpy_2.5.4.bb} (97%)