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:
v5.1.1
->v5.2.0
v2.25.12
->v2.26.6
v2.3.3
->v2.4.0
v1.9.0
->v1.10.1
Release Notes
actions/setup-python (actions/setup-python)
v5.2.0
Compare Source
github/codeql-action (github/codeql-action)
v2.26.6
Compare Source
v2.26.5
Compare Source
v2.26.4
Compare Source
v2.26.3
Compare Source
v2.26.2
Compare Source
v2.26.1
Compare Source
v2.26.0
Compare Source
v2.25.15
Compare Source
v2.25.14
Compare Source
v2.25.13
Compare Source
ossf/scorecard-action (ossf/scorecard-action)
v2.4.0
Compare Source
What's Changed
This update bumps the Scorecard version to the v5 release. For a complete list of changes, please refer to the v5.0.0 release notes. Of special note to Scorecard Action is the Maintainer Annotation feature, which can be used to suppress some Code Scanning false positives. Alerts will not be generated for any Scorecard Check with an annotation.
Documentation
New Contributors
Full Changelog: ossf/scorecard-action@v2.3.3...v2.4.0
pypa/gh-action-pypi-publish (pypa/gh-action-pypi-publish)
v1.10.1
Compare Source
🚑🔏 Oopsie... We missed a tiny bug in the attestations feature the other day
The problem was that the distribution file validity check was failing on any valid distribution being present and ready to be signed. What a silly mistake! It's now been fixed via pypa/gh-action-pypi-publish@0ab0b79, though. So everything's good!
-- @webknjaz💰
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.10.0...v1.10.1
🧔♂️ Release Manager: @webknjaz 🇺🇦
🙏 Special Thanks to @hugovk💰 for promptly validating the bug fix, mere minutes after I pushed it — I even haven't finished writing this text by then!
v1.10.0
Compare Source
🔏 Anything fancy, eh?
This time, @woodruffw💰 implemented support for PEP 740 attestations functionality in #236 and #245. This is a big deal, as it is a huge step forward to replacing what the deprecated GPG signatures used to provide in a more meaningful way.
🙏 And please, thank William for working on this amazing improvement for the ecosystem! The overall effort is tracked @&#https://github.com/pypi/warehouse/issues/15871/15871, by the way.
🪞 Full Diff: pypa/gh-action-pypi-publish@v1.9.0...v1.10.0
🧔♂️ Release Manager: @webknjaz 🇺🇦
Configuration
📅 Schedule: Branch creation - "before 6am on wednesday" in timezone Australia/Sydney, Automerge - At any time (no schedule defined).
🚦 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.