Release workflow failing and some warnings when building the package

[dalthviz]

Creating this issue to keep track of errors/warnings outputs generated when doing a release and that should be addressed at some point:

• Release workflow fails with the following message related with the actions/cache version:

Error: This request has been automatically failed because it uses a deprecated version of `actions/cache: v1`. Please update your workflow to use v3/v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

• Generated warning when running python -bb -X dev -W error -m build:

/tmp/build-env-afbw0_0q/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated
!!

        ********************************************************************************
        Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).

        By 2026-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  corresp(dist, value, root_dir)
/tmp/build-env-afbw0_0q/lib/python3.9/site-packages/setuptools/config/_apply_pyprojecttoml.py:55: SetuptoolsDeprecationWarning: 'tool.setuptools.license-files' is deprecated in favor of 'project.license-files' (available on setuptools>=77.0.0).
!!

        ********************************************************************************

        By 2026-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.
        ********************************************************************************

!!
  _apply_tool_table(dist, config, filename)

[ccordoba12]

For the release workflow we should use the PyPA Github action to upload packages securely instead of our own solution. I don't remember its name but it shouldn't be hard to find.

The other warning only requires to update the license name in pyproject.toml.

[krassowski]

That would be pypa/gh-action-pypi-publish which allows to create attestations and use trusted publishers easily.