Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 22, 2025

Updates the requirements on sigstore to permit the latest version.
Updates sigstore to 4.0.0

Release notes

Sourced from sigstore's releases.

v4.0.0

This is a major release with a host of API and functionality changes. The major new feature is Rekor v2 support but many other changes are also included, see list below.

Added

  • cli: Add --rekor-version to sign command arguments: This can be useful if Sigstore instance provides multiple Rekor versions and user wants to override the default choice #1471
  • cli: Support parallel signing. When multiple artifacts are signed, the Rekor requests are submitted in parallel: this is especially useful with Rekor v2. #1468, #1478, #1485
  • oidc (API): Allow custom audience claims via API #1402
  • rekor (API): Support Rekor v2 (aka rekor-tiles) in both verification and signing. #1370, #1422, #1432
  • trust (API): Make TrustedRoot, SigningConfig and ClientTrustConfig public API #1496

Changed

  • cli: Improve verify UX when wrong instance is used #1510
  • deps: replace sigstore_protobuf_specs dependency with sigstore-models #1470
  • trust: Update embedded TUF root #1515
  • trust (API): TrustConfig now provides the production()and staging() helpers. Similar methods were removed from SigningConfig, TrustedRoot, SigningContext and Issuer. Use TrustConfig everywhere in code base. #1363
  • trust (API): support SigningConfig v0.2, remove support for v0.1. The new format now fully defines the sigstore instance the client uses. SigningConfig class now has methods to return actual clients (like RekorClient) instead of just URLs for that sigstore instance. The --trust-config cli option now expects the trust config to contain a v0.2 SigningConfig. #1358, #1407
  • trust: Support ed25519 keys in trusted root #1377

Fixed

  • rekor: resolve circular import of LogEntry #1458
  • rekor: Fix checkpoint signature lookup when there are multiple signatures #1514
  • rekor: Fix entry handling so inclusion promise is optional #1382

... (truncated)

Changelog

Sourced from sigstore's changelog.

[4.0.0]

This is a major release with a host of API and functionality changes. The major new feature is Rekor v2 support but many other changes are also included, see list below.

Added

  • cli: Add --rekor-version to sign command arguments: This can be useful if Sigstore instance provides multiple Rekor versions and user wants to override the default choice #1471
  • cli: Support parallel signing. When multiple artifacts are signed, the Rekor requests are submitted in parallel: this is especially useful with Rekor v2. #1468, #1478, #1485
  • oidc (API): Allow custom audience claims via API #1402
  • rekor (API): Support Rekor v2 (aka rekor-tiles) in both verification and signing. #1370, #1422, #1432
  • trust (API): Make TrustedRoot, SigningConfig and ClientTrustConfig public API #1496

Changed

  • cli: Improve verify UX when wrong instance is used #1510
  • deps: replace sigstore_protobuf_specs dependency with sigstore-models #1470
  • trust: Update embedded TUF root #1515
  • trust (API): TrustConfig now provides the production()and staging() helpers. Similar methods were removed from SigningConfig, TrustedRoot, SigningContext and Issuer. Use TrustConfig everywhere in code base. #1363
  • trust (API): support SigningConfig v0.2, remove support for v0.1. The new format now fully defines the sigstore instance the client uses. SigningConfig class now has methods to return actual clients (like RekorClient) instead of just URLs for that sigstore instance. The --trust-config cli option now expects the trust config to contain a v0.2 SigningConfig. #1358, #1407
  • trust: Support ed25519 keys in trusted root #1377

Fixed

  • rekor: resolve circular import of LogEntry #1458
  • rekor: Fix checkpoint signature lookup when there are multiple signatures #1514
  • rekor: Fix entry handling so inclusion promise is optional #1382

... (truncated)

Commits
  • 7a9551f Prepare 4.0.0 release (#1541)
  • 83feb3d build(deps): bump pyopenssl from 25.2.0 to 25.3.0 (#1543)
  • 3b5632f build(deps): bump cryptography from 45.0.7 to 46.0.1 (#1544)
  • 365af7b build(deps): bump pyopenssl from 25.1.0 to 25.2.0 (#1542)
  • 5fac477 build(deps): update ruff requirement from <0.12.13 to <0.13.1 (#1539)
  • 2265c11 build(deps): bump github/codeql-action in the actions group (#1540)
  • ce00166 build(deps): bump github/codeql-action in the actions group (#1538)
  • 6f7d34f build(deps): bump the actions group with 2 updates (#1537)
  • 1630428 feat(models): expose TrustedRoot, SigningConfig, ClientTrustConfig (#1496)
  • f3af0dd build(deps): bump github/codeql-action in the actions group (#1535)
  • 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Updates the requirements on [sigstore](https://github.com/sigstore/sigstore-python) to permit the latest version.

Updates `sigstore` to 4.0.0
- [Release notes](https://github.com/sigstore/sigstore-python/releases)
- [Changelog](https://github.com/sigstore/sigstore-python/blob/main/CHANGELOG.md)
- [Commits](sigstore/sigstore-python@v3.5.3...v4.0.0)

---
updated-dependencies:
- dependency-name: sigstore
  dependency-version: 4.0.0
  dependency-type: direct:production
  dependency-group: python
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Sep 22, 2025
@jku
Copy link
Contributor

jku commented Oct 10, 2025

this can be handled in #132 (see later comments)

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 14, 2025

Looks like sigstore is no longer updatable, so this is no longer needed.

@dependabot dependabot bot closed this Oct 14, 2025
@dependabot dependabot bot deleted the dependabot/pip/python-ac22776dc0 branch October 14, 2025 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update Python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant