chore: bump the actions group with 4 updates

[dependabot]

Bumps the actions group with 4 updates: DavidAnson/markdownlint-cli2-action, pypa/gh-action-pypi-publish, crate-ci/typos and zizmorcore/zizmor-action.

Updates DavidAnson/markdownlint-cli2-action from 24.1.0 to 24.2.0

Commits

• 21c1be1 Update to version 24.2.0.
• cb5282d Freshen generated package-lock.json file, freshen generated index.js file.
• d36517c Add eslint-package-json/all to lint script, address new issues.
• 57b7f61 Refactor eslint.config.mjs to use defineConfig, change eslint-plugin-n from "...
• fe75d07 Address new lint error from previous commit, freshen generated index.js file.
• cea0e19 Bump eslint-plugin-unicorn from 71.1.0 to 72.0.0
• 5137af3 Freshen generated index.js file.
• ab8971b Bump markdownlint-cli2 from 0.23.1 to 0.23.2
• 92a0fc4 Bump actions/setup-node from 6 to 7
• 03ca1e4 Bump eslint from 10.6.0 to 10.7.0
• Additional commits viewable in compare view

Updates pypa/gh-action-pypi-publish from 1.14.1 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
• See full diff in compare view

Updates crate-ci/typos from 1.48.0 to 1.49.0

Release notes

Sourced from crate-ci/typos's releases.

v1.49.0

[1.49.0] - 2026-08-03

Features

• Updated the dictionary with the July 2026 changes

Changelog

Sourced from crate-ci/typos's changelog.

Change Log

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

[Unreleased] - ReleaseDate

[1.49.0] - 2026-08-03

Features

• Updated the dictionary with the July 2026 changes

[1.48.0] - 2026-06-30

Features

• Updated the dictionary with the June 2026 changes

[1.47.2] - 2026-06-04

Fixes

• Don't correct inferrable
• Correct unused inferible variant

[1.47.1] - 2026-06-03

Fixes

• Don't correct requestors

[1.47.0] - 2026-05-29

Features

• Updated the dictionary with the May 2026 changes

[1.46.3] - 2026-05-23

Fixes

• Don't correct to sequentials
• Don't correct to subdolder

[1.46.2] - 2026-05-16

Fixes

... (truncated)

Commits

• 8a48f81 chore: Release
• 2cfcb12 chore: Release
• 634a0fd chore: Release
• e58fe08 docs: Update changelog
• ff4b2ec Merge pull request #1588 from epage/july
• b7ef733 feat(dict): July updates
• 26e1ab0 Merge pull request #1586 from crate-ci/renovate/itertools-0.x
• 7d4352f chore(deps): Update Rust crate itertools to 0.15
• 3bc303c chore(deps): Update Rust Stable to v1.97 (#1580)
• 5ea8964 style: Make clippy happy
• Additional commits viewable in compare view

Updates zizmorcore/zizmor-action from 0.6.1 to 0.6.2

Release notes

Sourced from zizmorcore/zizmor-action's releases.

v0.6.2

zizmor 1.29.0 is now the default version.

Commits

• 3dc1ecc Sync zizmor versions (#149)
• dc57e30 chore(deps): bump the github-actions group with 3 updates (#147)
• d94880a README: bump pins (#146)
• 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