Update all - #268
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
🎯 Code Coverage (details) 🔗 Commit SHA: cdecbd6 | Docs | View more details | Give us feedback! |
renovate
Bot
force-pushed
the
renovate/all
branch
7 times, most recently
from
May 7, 2026 05:09
0194e70 to
821b4ca
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
May 15, 2026 13:42
3861862 to
c6c05d7
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
9 times, most recently
from
May 23, 2026 16:38
f8bf411 to
139d432
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
May 25, 2026 20:42
01b52e4 to
e649251
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
9 times, most recently
from
June 14, 2026 04:47
12023df to
f788a29
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
June 18, 2026 15:29
7683025 to
03774c0
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
June 24, 2026 21:45
b054800 to
f809f7c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #268 +/- ##
===========================
===========================
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
July 3, 2026 17:07
037c336 to
870e1ef
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
July 12, 2026 16:35
d9b25b5 to
33bda3d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.0.0→v1.0.5v6.0.2→v6.1.0v6.0.0→v6.3.0v7.0.0→v7.0.1v8.0.0→v8.3.2v6.0.0→v6.0.25d45857→4360b52v2.8.0→v2.9.0v4.0.0→v4.1.0v1.13.0→v1.14.2257e27e→f647ed73.12→3.14v1.2.2→v1.3.0v2.4.0→v2.6.2v2.62.27→v2.86.6v2.87.2(+4)Release Notes
DataDog/dd-sts-action (DataDog/dd-sts-action)
v1.0.5Compare Source
What's Changed
Full Changelog: DataDog/dd-sts-action@v1.0.4...v1.0.5
v1.0.4Compare Source
What's Changed
Full Changelog: DataDog/dd-sts-action@v1.0.3...v1.0.4
v1.0.3Compare Source
What's Changed
New Contributors
Full Changelog: DataDog/dd-sts-action@v1.0.2...v1.0.3
v1.0.2Compare Source
v1.0.1Compare Source
What's Changed
Full Changelog: DataDog/dd-sts-action@v1.0.0...v1.0.1
actions/checkout (actions/checkout)
v6.1.0Compare Source
v6.0.3Compare Source
actions/setup-python (actions/setup-python)
v6.3.0Compare Source
What's Changed
Enhancement
Dependency update
Documentation
New Contributors
Full Changelog: actions/setup-python@v6...v6.3.0
v6.2.0Compare Source
What's Changed
Dependency Upgrades
/__tests__/databy @dependabot in #1253 and #1264Full Changelog: actions/setup-python@v6...v6.2.0
v6.1.0Compare Source
What's Changed
Enhancements:
pip-installinput by @gowridurgad in #1201Dependency and Documentation updates:
allow-prereleasesby @yarikoptic in #979New Contributors
Full Changelog: actions/setup-python@v6...v6.1.0
actions/upload-artifact (actions/upload-artifact)
v7.0.1Compare Source
What's Changed
Full Changelog: actions/upload-artifact@v7...v7.0.1
astral-sh/setup-uv (astral-sh/setup-uv)
v8.3.2Compare Source
v8.3.1Compare Source
v8.3.0Compare Source
v8.2.0: 🌈 New inputsquietanddownload-from-astral-mirrorCompare Source
Changes
This release brings two new inputs and a few bug fixes.
New inputs
Lets talk about the new inputs first.
quiet
Pretty simple. It turns of all
infologgings. Useful if you use this in a composite action and are not interested in all the details.In the upcoming releases we will add log groups to fully implement support for "less noise"
download-from-astral-mirror
In some cases you may want to directly use the fallback of checking for available versions and downloading releases from GitHub instead of using the astral.sh mirror. Setting
download-from-astral-mirror: falseallows you to do that.Bugfixes
When using the astral.sh mirror to query available versions and download releases (done by default) we now stop sending the GitHub token in the header. The mirror never looked at it but we shouldn't be handing out that data even if it is just a short lived token.
All other bugfixes try to limit the impact of failed GitHub queries due to retries and other faults.
We couldn't pinpoint all rootcauses yet but added more logging for error cases to track them down.
🐛 Bug fixes
🚀 Enhancements
download-from-astral-mirrorinput @eifinger (#897)🧰 Maintenance
⬆️ Dependency updates
v8.1.0: 🌈 New inputno-projectCompare Source
Changes
This add the a new boolean input
no-project.It only makes sense to use in combination with
activate-environment: trueand will append--no projectto theuv venvcall. This is for example useful if you have a pyproject.toml file with parts unparseable by uv🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
codecov/codecov-action (codecov/codecov-action)
v6.0.2Compare Source
This is a copy of the
v7.0.0release to make updates easierWhat's Changed
Full Changelog: codecov/codecov-action@v6.0.1...v6.0.2
v6.0.1Compare Source
What's Changed
Full Changelog: codecov/codecov-action@v6.0.0...v6.0.1
lycheeverse/lychee-action (lycheeverse/lychee-action)
v2.9.0Compare Source
Summary
This release updates the default lychee version from
v0.23.0tov0.24.2.The main reason for this release is compatibility with the new lychee
0.24.xrelease artifacts. Starting with lycheev0.24.0, the archive layout changed, and thelycheebinary may now be packaged inside a subdirectory.lychee-actionnow detects that layout automatically, so users can upgrade without changing their workflows.If you use:
you will get the new version once the floating
v2tag has been updated. If you pin exact versions, update to:What’s new from lychee
v0.24.xBetter diagnostics
lychee now reports line and column numbers for detected links. This makes broken link reports easier to act on, especially in larger documentation sites or generated reports.
Text fragment checking
lychee can now check URL text fragments, such as links containing
#:~:text=.... This helps catch links that point to a valid page but no longer points to the intended highlighted text.Sitemap support
lychee can now read
sitemap.xmlinputs. This is useful for checking published websites or generated documentation sites where the sitemap is the easiest source of URLs to validate.JUnit output
lychee now supports JUnit output. This makes it easier to integrate link checking results with CI systems and test reporting tools that understand JUnit XML.
Redirect and remap visibility
lychee can now show redirects and remaps more clearly. This helps explain why a URL was checked as a different final URL and makes debugging link-checking behavior easier.
Multiple config files
lychee now supports multiple configuration files and expanded config handling. This is useful for repositories that split documentation, website, or package-specific link-checking settings.
Timeout handling
lychee can now accept timeouts explicitly. This gives users more control over how strict their link checks should be for flaky or slow endpoints.
Fixes and reliability improvements
Fixed lychee
0.24.xarchive compatibilitylychee-actionnow handles the new lychee release archive layout by detecting whether thelycheebinary is inside a subdirectory.This fixes compatibility with lychee
0.24.x.More stable installation path
The action now installs lychee into
$RUNNER_TEMP/lychee/bininstead of$HOME.This avoids failures on runners where
$HOMEdiffers between composite action steps. In those environments, the action could add one directory toPATHbut install the binary somewhere else, causinglychee: command not found.Safer automatic lychee version updates
The workflow that checks for new lychee releases now guards against
nullrelease versions before creating update PRs. This prevents invalid automated PRs such as “Update lycheeVersion to null”.Dependency updates
actions/checkoutfromv6tov7actions/cachefromv5tov6Upstream lychee changelog
For the full lychee changelog, see:
What’s Changed
$RUNNER_TEMPinstead of$HOMEby @mre in #338Full Changelog: lycheeverse/lychee-action@v2.8.0...v2.9.0
peaceiris/actions-gh-pages (peaceiris/actions-gh-pages)
v4.1.0: actions-github-pages v4.1.0Compare Source
See CHANGELOG.md for more details.
What's Changed
New Contributors
Full Changelog: peaceiris/actions-gh-pages@v4.0.0...v4.1.0
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.14.2Compare Source
This one probably won't touch you visibly so just bookmark @webknjaz's EuroPython 2026 “AI” slop rant for when it's published on YouTube or encourage him to come back with more to share next year!
🛠️ 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.
🧐 Tell me why..
The rest of the updates bump things related to
pypi-attestationsandsigstore, which has the most interesting backstory here. @facutuesca💰 sent a patch in #417 but a bunch more helped out.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
🪞 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.
v1.14.1Compare Source
This release was cut at EuroPython 2026 Sprints
🛠️ Internal Dependencies
@adisivaprasad💰 helped get rid of the GitHub Actions runner warning about the old Node 20 runtime being used by updating
actions/setup-pythonfrom v5.6.0 to v6.2.0 in #408.💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.14.0...v1.14.1
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @jylenhof💰 for reminding me to work on this release!
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
v1.14.0Compare Source
Audit your supply chain regularly!
✨ What's Changed
The main change in this release is that
verboseandprint-hashinputs are now on by default. This was contributed by @whitequark💰 in #397.📝 Docs
@woodruffw💰 updated the mentions of PEP 740 to stop implying that it might be experimental (it hasn't been for quite a while!) in #388 and @him2him2💰 brushed up some grammar in the README and SECURITY docs via #395.
🛠️ Internal Updates
@woodruffw💰 bumped
sigstoreandpypi-attestationsin the lock file (#391) and @webknjaz💰 added infra for using type annotations in the project (#381).💪 New Contributors
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.13.0...v1.14.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @facutuesca💰 and @woodruffw💰 for helping maintain this project when I can't!
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
actions/python-versions (python)
v3.14.7: 3.14.7Compare Source
Python 3.14.7
v3.14.6: 3.14.6Compare Source
Python 3.14.6
v3.14.5: 3.14.5Compare Source
Python 3.14.5
v3.14.4: 3.14.4Compare Source
Python 3.14.4
v3.14.3: 3.14.3Compare Source
Python 3.14.3
v3.14.2: 3.14.2Compare Source
Python 3.14.2
v3.14.1: 3.14.1Compare Source
Python 3.14.1
v3.14.0: 3.14.0Compare Source
Python 3.14.0
v3.13.15: 3.13.15Compare Source
Python 3.13.15
v3.13.14: 3.13.14Compare Source
Python 3.13.14
v3.13.13: 3.13.13Compare Source
Python 3.13.13
v3.13.12: 3.13.12Compare Source
Python 3.13.12
v3.13.11: 3.13.11Compare Source
Python 3.13.11
v3.13.10: 3.13.10Compare Source
Python 3.13.10
v3.13.9: 3.13.9Compare Source
Python 3.13.9
v3.13.8: 3.13.8Compare Source
Python 3.13.8
v3.13.7: 3.13.7Compare Source
Python 3.13.7
v3.13.6: 3.13.6Compare Source
Python 3.13.6
v3.13.5: 3.13.5Compare Source
Python 3.13.5
v3.13.4: 3.13.4Compare Source
Python 3.13.4
v3.13.3: 3.13.3Compare Source
Python 3.13.3
v3.13.2: 3.13.2Compare Source
Python 3.13.2
v3.13.1: 3.13.1Compare Source
Python 3.13.1
v3.13.0: 3.13.0Compare Source
Python 3.13.0
re-actors/alls-green (re-actors/alls-green)
v1.3.0Compare Source
Sometimes these releases take time. Cherish it.
🛡️ What's Unmessed
✨ What's Improved
I did a bunch of internal refactoring including hints of what @max-sixty💰 reported in #23. And took a small patch of @krokofant💰 in. This involved a bunch of preparatory infra work with testing infra.
One notable improvement is that now thanks to @tomasr8💰's and @hugovk💰's UX suggestions in #31, the gate status output is colored in the console and should be easier to scan in the log output per line. They entries now have leading
✓/❌acceptance marks and the actual incoming job outcomes are labeled with🟢/🔴/⬜/⚫.🐛 What's Fixed
The job-statuses summary could print "Some of the allowed to be skipped jobs did not succeed" based on the wrong condition — it's now tied to
allowed-skipsas intended, notallowed-failures.💪 New Contributors
🪞 Full Diff: re-actors/alls-green@v1.2.2...v1.3.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
💬 Discuss on Bluesky 🦋, on Mastodon 🐘 and on GitHub.
softprops/action-gh-release (softprops/action-gh-release)
v2.6.2Compare Source
What's Changed
Other Changes 🔄
Full Changelog: softprops/action-gh-release@v2...v2.6.2
v2.6.1Compare Source
2.6.1is a patch release focused on restoring linked discussion thread creation whendiscussion_category_nameis set. It fixes#764, where the draft-first publish flowstopped carrying the discussion category through the final publish step.
If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.
What's Changed
Bug fixes 🐛
v2.6.0Compare Source
2.6.0is a minor release centered onprevious_tagsupport forgenerate_release_notes,which lets workflows pin GitHub's comparison base explicitly instead of relying on the default range.
It also includes the recent concurrent asset upload recovery fix, a
working_directorydocs sync,a checked-bundle freshness guard for maintainers, and clearer immutable-prerelease guidance where
GitHub platform behavior imposes constraints on how prerelease asset uploads can be published.
If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.
What's Changed
Exciting New Features 🎉
Bug fixes 🐛
Other Changes 🔄
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.