1
0
mirror of https://github.com/pypa/gh-action-pypi-publish synced 2024-11-30 21:22:28 +08:00

Compare commits

...

6 Commits

Author SHA1 Message Date
Brendon Smith
438644dd34
Merge 54e5a03d42 into fb13cb3069 2024-10-30 02:25:03 +01:00
Sviatoslav Sydorenko
fb13cb3069
📝 Reflect the PR #277 changes in README
This makes minimum modifications to indicate that `attestations` is
not on by default.
2024-10-30 02:20:55 +01:00
Sviatoslav Sydorenko
72ead1a85a
Merge PRs #276 and #277 into release/v1 2024-10-30 02:04:39 +01:00
William Woodruff
0126dcac8e
action: enable attestations by default
Signed-off-by: William Woodruff <william@trailofbits.com>
2024-10-28 14:31:58 -04:00
William Woodruff
335e8b00ae
bump sigstore==3.5.1
Signed-off-by: William Woodruff <william@trailofbits.com>
2024-10-28 14:29:41 -04:00
William Woodruff
1545e96dcb
requirements: bump sigstore, pypi-attestations
Signed-off-by: William Woodruff <william@trailofbits.com>
2024-10-22 12:40:04 -04:00
4 changed files with 14 additions and 11 deletions

View File

@ -111,16 +111,17 @@ filter to the job:
> Generating and uploading digital attestations currently requires > Generating and uploading digital attestations currently requires
> authentication with a [trusted publisher]. > authentication with a [trusted publisher].
You can generate signed [digital attestations] for all the distribution files and Generating signed [digital attestations] for all the distribution files
upload them all together by enabling the `attestations` setting: and uploading them all together is now on by default for all projects
using Trusted Publishing. To disable it, set `attestations` as follows:
```yml ```yml
with: with:
attestations: true attestations: false
``` ```
This will use [Sigstore] to create attestation The attestation objects are created using [Sigstore] for each
objects for each distribution package, signing them with the identity provided distribution package, signing them with the identity provided
by the GitHub's OIDC token associated with the current workflow. This means by the GitHub's OIDC token associated with the current workflow. This means
both the trusted publishing authentication and the attestations are tied to the both the trusted publishing authentication and the attestations are tied to the
same identity. same identity.

View File

@ -86,7 +86,7 @@ inputs:
Enable experimental support for PEP 740 attestations. Enable experimental support for PEP 740 attestations.
Only works with PyPI and TestPyPI via Trusted Publishing. Only works with PyPI and TestPyPI via Trusted Publishing.
required: false required: false
default: 'false' default: 'true'
branding: branding:
color: yellow color: yellow
icon: upload-cloud icon: upload-cloud

View File

@ -10,8 +10,8 @@ id ~= 1.0
requests requests
# NOTE: Used to generate attestations. # NOTE: Used to generate attestations.
pypi-attestations ~= 0.0.12 pypi-attestations ~= 0.0.13
sigstore ~= 3.2.0 sigstore ~= 3.5.1
# NOTE: Used to detect the PyPI package name from the distribution files # NOTE: Used to detect the PyPI package name from the distribution files
packaging packaging

View File

@ -72,7 +72,9 @@ pkginfo==1.10.0
platformdirs==4.2.2 platformdirs==4.2.2
# via sigstore # via sigstore
pyasn1==0.6.0 pyasn1==0.6.0
# via sigstore # via
# pypi-attestations
# sigstore
pycparser==2.22 pycparser==2.22
# via cffi # via cffi
pydantic==2.7.1 pydantic==2.7.1
@ -91,7 +93,7 @@ pyjwt==2.8.0
# via sigstore # via sigstore
pyopenssl==24.1.0 pyopenssl==24.1.0
# via sigstore # via sigstore
pypi-attestations==0.0.12 pypi-attestations==0.0.13
# via -r runtime.in # via -r runtime.in
python-dateutil==2.9.0.post0 python-dateutil==2.9.0.post0
# via betterproto # via betterproto
@ -117,7 +119,7 @@ rich==13.7.1
# twine # twine
securesystemslib==1.0.0 securesystemslib==1.0.0
# via tuf # via tuf
sigstore==3.2.0 sigstore==3.5.1
# via # via
# -r runtime.in # -r runtime.in
# pypi-attestations # pypi-attestations