Bump pypi-attestations from 0.0.21 to 0.0.24

[dependabot]

Bumps pypi-attestations from 0.0.21 to 0.0.24.

Release notes

Sourced from pypi-attestations's releases.

v0.0.24

Added

• The GooglePublisher type has been added to support Google Cloud-based Trusted Publishers (#114)

v0.0.23

Added

• The CLI has a new subcommand convert, which takes a Sigstore bundle and converts it to a PEP 740 attestation.

Changed

• The Attestation.verify(...) API has been changed to accept an offline parameter that, when True, disables TUF refreshes.
• The CLI verify commands now also accept an --offline flag that disables TUF refreshes. Additionally, when used with the verify pypi subcommand, the --offline flag enforces that the distribution and provenance file arguments must be local file paths.

Fixed

• Fixed a bug where GitHubPublisher policy verification would fail if the Source Repository Ref or Source Repository Digest claim was missing from the attestation's certificate. We require at least one of the two claims, but not necessarily both (#109)

v0.0.22

Changed

• The inspect subcommand now ignores inputs that don't match *.attestation, rather than failing on them (#93)

Added

• The CLI subcommand verify attestation now supports .slsa.attestation files. When verifying an artifact, both .publish.attestation and .slsa.attestation files are used (if present).
• The CLI subcommand verify pypi now supports a friendlier syntax to specify the artifact to verify. The artifact can now be specified with a pypi: prefix followed by the filename, e.g: pypi:sampleproject-1.0.0.tar.gz. The old way (passing the direct URL) is still supported.
• The CLI subcommand verify pypi now supports passing the local paths to the artifact and its provenance file, allowing the user to verify files already downloaded from PyPI. The artifact path is passed as

... (truncated)

Changelog

Sourced from pypi-attestations's changelog.

[0.0.24]

Added

• The GooglePublisher type has been added to support Google Cloud-based Trusted Publishers (#114)

[0.0.23]

Added

• The CLI has a new subcommand convert, which takes a Sigstore bundle and converts it to a PEP 740 attestation.

Changed

• The Attestation.verify(...) API has been changed to accept an offline parameter that, when True, disables TUF refreshes.
• The CLI verify commands now also accept an --offline flag that disables TUF refreshes. Additionally, when used with the verify pypi subcommand, the --offline flag enforces that the distribution and provenance file arguments must be local file paths.

Fixed

• Fixed a bug where GitHubPublisher policy verification would fail if the Source Repository Ref or Source Repository Digest claim was missing from the attestation's certificate. We require at least one of the two claims, but not necessarily both (#109)

[0.0.22]

Changed

• The inspect subcommand now ignores inputs that don't match *.attestation, rather than failing on them (#93)

Added

• The CLI subcommand verify attestation now supports .slsa.attestation files. When verifying an artifact, both .publish.attestation and .slsa.attestation files are used (if present).
• The CLI subcommand verify pypi now supports a friendlier syntax to specify the artifact to verify. The artifact can now be specified with a pypi: prefix followed by the filename, e.g: pypi:sampleproject-1.0.0.tar.gz. The old way (passing the direct URL) is still supported.

... (truncated)

Commits

• 69036f5 chore: prep for release v0.0.24
• c8012e8 feat: add support for Google Cloud-based Trusted Publishers (#114)
• 22cc304 pypi_attestations: bump version to 0.0.23 (#110)
• 5736314 bugfix: impl: require at least one of the source ref/sha extensions (#109)
• 7f041da build(deps): bump actions/setup-python in the actions group (#108)
• fc353f7 build(deps): bump the actions group with 2 updates
• 9abcb40 _cli: Add command to convert Sigstore bundles to attestations (#105)
• 6885434 Remove extra symbol in noqa annotation
• 29fc359 build(deps): bump actions/download-artifact in the actions group
• 2058510 Add API and CLI option for offline (no TUF refresh) verification (#104)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #34.