Upgrade to sigstore 4.0.0#289
Draft
Uh oh!
There was an error while loading. Please reload this page.
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.
Split out from #283.
cc @sethmlarson, @woodruffw
The flow here is:
run_release.pyis run on the release manager's machine. That pops open the sigstore auth page, and fetches an identity token.SIGSTORE_IDENTITY_TOKENenv var, for when the sigstore CLI is run byadd_to_pydotorg.pyon the downloads server, where the file signing happens.I can also give this a demo run with 3.15.0a1 next week.