Bump the actions group across 1 directory with 3 updates

[dependabot]

Bumps the actions group with 3 updates in the / directory: OpenAstronomy/github-actions-workflows/.github/workflows/tox.yml, actions/setup-python and pypa/gh-action-pypi-publish.

Updates OpenAstronomy/github-actions-workflows/.github/workflows/tox.yml from 2 to 3

Release notes

Sourced from OpenAstronomy/github-actions-workflows/.github/workflows/tox.yml's releases.

v3.0.0

Breaking Changes

• If a value is provided for coverage uploading (coverage: codecov, coverage: codecov-oidc, or coverage: github), tests must end with a .coverage file at the workspace root. Use the COVERAGE_FILE environment variable; for instance, you can set it explicitly in tox.ini. See the relevant section of the docs for more information.

  set_env =
    COVERAGE_FILE={toxinidir}/.coverage

• The fill:, fill_platforms:, and fill_factors: inputs are now removed in favor of using version glob syntax py3* directly in envs:. For example, to produce the following set of envs:

      envs: |
         - linux: pep8
           pytest: false
         - linux: py311-xdist
         - linux: py312-xdist
         - linux: py313-xdist
         - linux: py314-xdist
         - macos: py311-xdist
         - macos: py312-xdist
         - macos: py313-xdist
         - macos: py314-xdist

  on OpenAstronomy/github-actions-workflows@v2 you would have used fill:, fill_platforms:, and fill_factors::

   uses: OpenAstronomy/github-actions-workflows/.github/workflows/tox.yml@v2
     with:
       envs: |
         - linux: pep8
           pytest: false
       fill: true
       fill_platforms: linux,macos
       fill_factors: xdist

  but now with OpenAstronomy/github-actions-workflows@v3 you use a py* version glob instead:

   uses: OpenAstronomy/github-actions-workflows/.github/workflows/tox.yml@v3
     with:
       envs: |
         - linux: pep8
           pytest: false
         - linux: py3*-xdist
         - macos: py3*-xdist

What's Changed

• Coverage reporting refactor and cleanup by @​Cadair in OpenAstronomy/github-actions-workflows#397
• Update codecov/codecov-action to 7.0 to fix signature error by @​Cadair in OpenAstronomy/github-actions-workflows#400
• Better Reporting of Coverage Reporting Errors by @​Cadair in OpenAstronomy/github-actions-workflows#399

... (truncated)

Commits

• 8c8bb6c DEP: allow running python helper scripts with any Python 3.12.x patch version...
• e5af21e fix bug in passing workflow repo to supported-pythons (#405)
• 6ae6691 replace fill: parameter with logic to expand py3* glob syntax in envs
• 8b63a9c DEP: upgrade Github Action dependencies (#398)
• 8449fec DEP: upgrade cibuildwheel to 4.0.0 (#393)
• 5d99eb3 Disable codecov comments (#401)
• a7a7c50 Better Reporting of Coverage Reporting Errors (#399)
• ade42af Update codecov/codecov-action to 7.0 to fix signature error
• e113052 Coverage reporting refactor and cleanup (#397)
• See full diff in compare view

Updates actions/setup-python from 6.3.0 to 7.0.0

Release notes

Sourced from actions/setup-python's releases.

v7.0.0

What's Changed

Enhancements

• Migrate to ESM and upgrade dependencies by @​priyagupta108 in actions/setup-python#1330
• Pin SHA commits and update docs with latest versions by @​HarithaVattikuti in actions/setup-python#1338
• Remove the pip-install input by @​gowridurgad in actions/setup-python#1336

Bug Fix

• Fix to Classify stderr warning messages as warnings instead of errors in annotations by @​lmvysakh in actions/setup-python#1335
• Validate and retry manifest fetch to prevent silent failures by @​priyagupta108 in actions/setup-python#1332

Dependency Upgrade

• Bump certifi from 2020.6.20 to 2024.7.4 in /tests/data by @​dependabot in actions/setup-python#1328
• Remove EOL Python versions and Bumps numpy text fixture by @​priya-kinthali in actions/setup-python#1333
• Upgrade @​actions/cache to 6.2.0 by @​philip-gai in actions/setup-python#1337

New Contributors

• @​lmvysakh made their first contribution in actions/setup-python#1335
• @​philip-gai made their first contribution in actions/setup-python#1337

Full Changelog: actions/setup-python@v6...v7.0.0

Commits

• 5fda3b9 Pin SHA commits and update docs with latest versions (#1338)
• 4ab7e95 Merge pull request #1337 from actions/philip-gai/bump-actions-cache-6-2-0
• 0f3a009 Remove the pip-install input (#1336)
• f8cf429 Migrate to ESM and upgrade dependencies (#1330)
• 54baeea Validate and retry manifest fetch to prevent silent failures (#1332)
• c709277 Annotation code fix (#1335)
• 6849080 remove EOL Python versions and Bumps numpy text fixture (#1333)
• 0903b46 Bump certifi from 2020.6.20 to 2024.7.4 in /tests/data (#1328)
• See full diff in compare view

Updates pypa/gh-action-pypi-publish from 1.14.0 to 1.14.2

Release notes

Sourced from pypa/gh-action-pypi-publish's releases.

v1.14.2

🛠️ Urgh… Another release!? Again? Explain yourself!

Looking at the diff, you'll only witness updates across the dependency tree. That's it! It's not a security fix or anything like that even, no. But you'll want this update.

[!tip] So what most people will find useful is @​takluyver💰's update of Twine to v7 that we use internally (#416). This version will let them upload their sdists and wheels containing core packaging metadata v2.5 to (Test)PyPI.

🧐 Tell me why..

TL;DR non-pure-python projects with C-extensions tend to have dozens (sometimes hundreds) wheels to upload to PyPI per release. They are often quite big and take time to transfer over the network. People started noticing problems and coming up with DIY sharding workarounds like aio-libs/aiohttp#13226 around July 23. On this date, projects with a good amount of bytes to publish would start getting timeouts 5 minutes after the PyPI publishing job begun. The same job that worked just fine before.

I had to start pinging upstream library and ecosystem people, on GitHub and privately, to start making sense of what was happening. Eventually, we collectively concluded that GitHub must've shortened the lifetime of their OIDC identity — it seems to have used to be 10 minutes long (at some point in the past) and is now 5 minutes, apparently. It's not documented clearly, and we have not been able to get any clarity by attempting to contact GitHub through private channels, using personal connections.

Over the course of investigation, @​facutuesca💰 found and fixed a related underlying cache invalidation bug in sigstore/sigstore-python#1838, which he then coordinated propagation through the dependency chain updates in sigstore-python, pypi-attestations, gh-action-pypi-publish and gh-action-sigstore-python.

Mike's also discovered that Sigstore's Rekor slowdown seems to have become the main contributing cause of the last week's incident. He's collected some data to support this claim: https://publishing-five-minute-timeout.tiiny.site.

🫶 New Contributors

• @​davidbrochart made their first contribution in #415
• @​takluyver made their first contribution in #416

🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.1...v1.14.2

🧔‍♂️ Release Manager: @​webknjaz 🇺🇦

🙏 Special Thanks to @​davidbrochart💰 and @​Dreamsorcerer💰 for turning my attention (in #415 and in private) to the newly surfaced corner case in GitHub's behavior that only affected a narrow category of projects while many others remained blissfully unaware. @​bdraco💰 came up with a DIY sharding workaround for aiohttp that served as a demo for other projects. @​miketheman💰 confirmed the Warehouse-side details. Also, @​jku💰 and @​woodruffw💰 helped work through, review and release the Sigstore ecosystem upstream libs.

💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and [on GitHub][release discussion].

[![GH Sponsors badge]][GH Sponsors URL]

... (truncated)

Commits

• dc37677 Merge pull request #417 from trail-of-forks/ft/bump-deps
• 8b2f234 Bump pypi-attestations and sigstore
• 78b72db Merge pull request #416 from takluyver/twine-v7
• 92f4d2a Update twine to v7
• ba38be9 Merge pull request #408 from adisivaprasad/bump-setup-python-v6
• a6c5088 Bump actions/setup-python from v5.6.0 to v6.2.0
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions