File tree Expand file tree Collapse file tree 1 file changed +21
-0
lines changed Expand file tree Collapse file tree 1 file changed +21
-0
lines changed Original file line number Diff line number Diff line change @@ -246,6 +246,25 @@ for example. See [Creating & using secrets]. While still secure,
246
246
[trusted publishing] is now encouraged over API tokens as a best practice
247
247
on supported platforms (like GitHub).
248
248
249
+ # ## Generating and uploading attestations (EXPERIMENTAL)
250
+
251
+ > [!NOTE]
252
+ > Support for generating and uploading [PEP 740 attestations] is currently
253
+ > experimental and limited only to Trusted Publishing flows using PyPI or TestPyPI.
254
+
255
+ You can generate signed [PEP 740 attestations] for all the distribution files and
256
+ upload them all together by enabling the `attestations` setting :
257
+
258
+ ` ` ` yml
259
+ with:
260
+ attestations: true
261
+ ` ` `
262
+
263
+ This will use `sigstore` to create attestation objects for each distribution package,
264
+ signing them with the identity provided by the GitHub's OIDC token associated with the
265
+ current workflow. This means both the trusted publishing authentication and the
266
+ attestations are tied to the same identity.
267
+
249
268
# # License
250
269
251
270
The Dockerfile and associated scripts and documentation in this project
@@ -287,3 +306,5 @@ https://github.com/vshymanskyy/StandWithUkraine/blob/main/docs/README.md
287
306
[configured on PyPI] : https://docs.pypi.org/trusted-publishers/adding-a-publisher/
288
307
289
308
[how to specify username and password] : # specifying-a-different-username
309
+
310
+ [PEP 740 attestations] : https://peps.python.org/pep-0740/
You can’t perform that action at this time.
0 commit comments