xz 5.8.1 is already installed and up-to-date. To reinstall 5.8.1, run: brew reinstall xz

openssl@3 3.5.2 is already installed and up-to-date. To reinstall 3.5.2, run: brew reinstall openssl@3

ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja

pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf

xz 5.8.1 is already installed and up-to-date. To reinstall 5.8.1, run: brew reinstall xz

openssl@3 3.5.2 is already installed and up-to-date. To reinstall 3.5.2, run: brew reinstall openssl@3

ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja

libtool 2.5.4 is already installed and up-to-date. To reinstall 2.5.4, run: brew reinstall libtool

autoconf 2.72 is already installed and up-to-date. To reinstall 2.72, run: brew reinstall autoconf

pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf

Input 'packages_dir' has been deprecated with message: The inputs have been normalized to use kebab-case. Use `packages-dir` instead.

A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers

The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.