Update sigstore/gh-action-sigstore-python action to v3 #75
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:
v2.1.1
->v3.0.0
Release Notes
sigstore/gh-action-sigstore-python (sigstore/gh-action-sigstore-python)
v3.0.0
Compare Source
Added
inputs
now allows recursive globbing with**
(#106)
Removed
fulcio-url
,rekor-url
,ctfe
,rekor-root-pubkey
(#140)
signature
,certificate
,bundle
(#146)
Changed
inputs
is now parsed according to POSIX shell lexing rules, improvingthe action's consistency when used with filenames containing whitespace
or other significant characters
(#104)
inputs
is now optional ifrelease-signing-artifacts
is trueand the action's event is a
release
event. In this case, the actiontakes no explicit inputs, but signs the source archives already attached
to the associated release
(#110)
The default suffix has changed from
.sigstore
to.sigstore.json
,per Sigstore's client specification
(#140)
release-signing-artifacts
now defaults totrue
(#142)
Fixed
The
release-signing-artifacts
setting no longer causes a hard errorwhen used under the incorrect event
(#103)
Various deprecations present in
sigstore-python
's 2.x series have beenresolved
(#140)
This workflow now supports CI runners that use PEP 668 to constrain global
package prefixes
(#145)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.