NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #3727 most downloaded on PyPI
A tool for signing Python package distributions
Last release 2 months ago
28 Jul 2026
Release timing varies
gaps range from 2 weeks to 4 months
Nearly every release is documented
notes for 47 of 47 stable releases
9 versions withdrawn
withdrawn after publishing
4 years old
66 releases · first in 2022
One column per quarter.
A valid certificate is used during signing even if the underlying identity token has already expired by @facutuesca in https://github.com/sigstore/sig
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v4.4.0...v4.5.0
sigstore no longer limits the upper-bound of cryptography in order to be less disruptive to downstream integrators.
sigstore no longer limits the upper-bound of cryptography in order to be less disruptive to downstream integrators.
(#1811)sub claim containing a non-ASCII environment name). The CSR subject is unused by Fulcio, so it is now omitted entirely
(#1507)Full Changelog: https://github.com/sigstore/sigstore-python/compare/v4.3.0...v4.4.0
Issuer.identity_token accepts an optional redirect_port argument to accomodate OIDC providers that require pre-registered redirect URIs
Issuer.identity_token accepts an optional redirect_port argument to
accomodate OIDC providers that require pre-registered redirect URIs
(#1029)This release fixes a minor security issue in OIDC authentication and a compatibility issue with Fulcio Signed Certificate Timestamps. All users are re
This release fixes a minor security issue in OIDC authentication and a compatibility issue with Fulcio Signed Certificate Timestamps. All users are recommended to upgrade.
cli: Support using other Sigstore instances with --instance URL. New instances are trusted with new top level command trust-instance ROOTFILE. #1548
--instance URL.
New instances are trusted with new top level command trust-instance ROOTFILE.
#1548This 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 includ
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.
--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
#1471production()and staging() helpers. Similar methods were removed from
SigningConfig, TrustedRoot, SigningContext and Issuer. Use TrustConfig everywhere in code base.
#1363SigningConfig 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, #1407Full Changelog: https://github.com/sigstore/sigstore-python/compare/v3.6.5...v4.0.0
This release backports a minor security issue in OIDC authentication and a compatibility issue in Fulcios Signed Certificate Timestamps to the 3.6.x s
This release backports a minor security issue in OIDC authentication and a compatibility issue in Fulcios Signed Certificate Timestamps to the 3.6.x series. All users are advised to upgrade to 4.2.0 or 3.6.7
Improved error message when verifying bundles with rekor v2 entries
Fixed verified time handling so that additional timestamps cannot break otherwise valid signature bundles
Bumped the rfc3161-client dependency to >=1.0.3 to fix a security vulnerability
rfc3161-client dependency to >=1.0.3 to fix a security
vulnerability (#1451)Verify: Avoid hard failure if trusted root contains unsupported keytypes (as verification may succeed without that key). #1425
A small bug fix release.
Fixed issue where a trust root with multiple rekor keys was not considered valid: Now any rekor key listed in the trust root is considered good to ver
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v3.6.1...v3.6.2
Relaxed the transitive dependency on cryptography to allow v43 and v44 to be resolved
cryptography to allow v43 and v44
to be resolved
(#1251)API: The DSSE Envelope class now performs automatic validation
API: The DSSE Envelope class now performs automatic validation
(#1211)
API: Added signature property to Envelope class for accessing raw
signature bytes (#1211)
Signed timestamps embedded in bundles are now automatically verified against Timestamp Authorities provided within the Trusted Root ([#1206] (https://github.com/sigstore/sigstore-python/pull/1206))
Bundles are now generated with signed timestamps when signing if the Trusted Root contains one or more Timestamp Authorities (#1216)
This is the last planned release in 3.5.x series: All users should upgrade to a newer release series.
This is the last planned release in 3.5.x series: All users should upgrade to a newer release series.
### Fixed * Corrective release for [3.5.2]
Fixed a CLI parsing bug introduced in 3.5.0 when attempting to suppress irrelevant warnings
CLI: The sigstore plumbing update-trust-root command has been added. Like other plumbing-level commands, this is considered unstable and changes are n
sigstore plumbing update-trust-root command has been added.
Like other plumbing-level commands, this is considered unstable and
changes are not subject to our semver policy until explicitly noted
(#1174).crt/.sig
inputs (#1179)CLI: When verifying, the --offline flag now fully disables all online operations, including routine local TUF repository refreshes
CLI: When verifying, the --offline flag now fully disables all online
operations, including routine local TUF repository refreshes
(#1143)
sigstore-python's minimum supported Python version is now 3.9
sigstore verify subcommands now always check for a matching
input file, rather than unconditionally falling back to matching on a
valid sha256:... digest pattern
(#1152)CLI: The sigstore verify command now outputs the inner in-toto statement when verifying DSSE envelopes. If verification is successful, the output will
CLI: The sigstore verify command now outputs the inner in-toto statement
when verifying DSSE envelopes. If verification is successful, the output
will be the inner in-toto statement. This allows the user to see the
statement's predicate, which sigstore-python does not verify and should be
verified by the user.
CLI: The sigstore attest subcommand has been added. This command is
similar to cosign attest in that it signs over an artifact and a
predicate using a DSSE envelope. This commands requires the user to pass
a path to the file containing the predicate, and the predicate type.
Currently only the SLSA Provenance v0.2 and v1.0 types are supported.
CLI: The sigstore verify command now supports verifying digests. This means
that the user can now pass a digest like sha256:aaaa.... instead of the
path to an artifact, and sigstore-python will verify it as if it was the
artifact with that digest.
API: models.Bundle.BundleType is now a public API
API: models.Bundle.BundleType is now a public API
(#1089)
CLI: The sigstore plumbing subcommand hierarchy has been added. This
hierarchy is for developer-only interactions, such as fixing malformed
Sigstore bundles. These subcommands are not considered stable until
explicitly documented as such.
(#1089)
stderr, rather than stdout
(#1089)API: dsse.StatementBuilder has been added. It can be used to construct an in-toto Statement for subsequent enveloping and signing. This API is public
API: dsse.StatementBuilder has been added. It can be used to construct an
in-toto Statement for subsequent enveloping and signing.
This API is public but is not considered stable until the next major
release.
(#1077)
API: dsse.Digest, dsse.DigestSet, and dsse.Subject have been added.
These types can be used with the StatementBuilder API as part of in-toto
Statement construction.
These API are public but are not considered stable until the next major
release.
(#1078)
verify_dsse now rejects bundles with DSSE envelopes that have more than
one signature, rather than checking all signatures against the same key
(#1062)Maintainers' note: this is a major release, with significant public API and CLI changes. We strongly recommend you read the entries below to fully und
Maintainers' note: this is a major release, with significant public API and CLI
changes. We strongly recommend you read the entries below to fully
understand the changes between 2.x and 3.x.
API: Signer.sign_artifact() has been added, replacing the removed
Signer.sign() API
API: Signer.sign_dsse() has been added. It takes an in-toto Statement
as an input, producing a DSSE-formatted signature rather than a "bare"
signature (#804)
API: "v3" Sigstore bundles are now supported during verification (#901)
API: Verifier.verify(...) can now take a Hashed as an input, performing
signature verification on a pre-computed hash value
(#904)
API: The sigstore.dsse module has been been added, including APIs
for representing in-toto statements and DSSE envelopes
(#930)
CLI: The --trust-config flag has been added as a global option,
enabling consistent "BYO PKI" uses of sigstore with a single flag
(#1010)
CLI: The sigstore verify subcommands can now verify bundles containing
DSSE entries, such as those produced by
GitHub Artifact Attestations
(#1015)
BREAKING API CHANGE: SigningResult has been removed.
The public signing APIs now return sigstore.models.Bundle.
BREAKING API CHANGE: VerificationMaterials has been removed.
The public verification APIs now accept sigstore.models.Bundle.
BREAKING API CHANGE: Signer.sign(...) has been removed. Use
either sign_artifact(...) or sign_dsse(...), depending on whether
you're signing opaque bytes or an in-toto statement.
BREAKING API CHANGE: VerificationResult has been removed.
The public verification and policy APIs now raise
sigstore.errors.VerificationError on failure.
BREAKING CLI CHANGE: The --rekor-url and --fulcio-url
flags have been entirely removed. To configure a custom PKI, use
--trust-config
(#1010)
BREAKING API CHANGE: Verifier.verify(...) now takes a bytes | Hashed
as its verification input, rather than implicitly receiving the input through
the VerificationMaterials parameter
(#904)
BREAKING API CHANGE: VerificationMaterials.rekor_entry(...) now takes
a Hashed parameter to convey the digest used for Rekor entry lookup
(#904)
BREAKING API CHANGE: Verifier.verify(...) now takes a sigstore.models.Bundle,
instead of a VerificationMaterials (#937)
BREAKING CLI CHANGE: sigstore sign now emits {input}.sigstore.json
by default instead of {input}.sigstore, per the client specification
(#1007)
sigstore-python now requires inclusion proofs in all signing and verification flows, regardless of bundle version of input types. Inputs that do not have an inclusion proof (such as detached materials) cause an online lookup before any further processing is performed (#937)
sigstore-python now generates "v3" bundles by default during signing (#937)
CLI: Bundles are now always verified offline. The offline flag has no effect. (#937)
CLI: "Detached" materials are now always verified online, due to a lack of
an inclusion proof. Passing --offline with detached materials will cause
an error (#937)
API: sigstore.transparency has been removed, and its pre-existing APIs
have been re-homed under sigstore.models
(#990)
API: oidc.IdentityToken.expected_certificate_subject has been renamed
to oidc.IdentityToken.federated_issuer to better describe what it actually
contains. No functional changes have been made to it
(#1016)
API: policy.Identity now takes an optional OIDC issuer, rather than a
required one (#1015)
CLI: sigstore verify github now requires --cert-identity or
--repository, not just --cert-identity
(#1015)
Nothing published for this version
Nothing published for this version
This is a bug fix release to fix the release pipeline that failed for 2.1.4 release.
This is a bug fix release to fix the release pipeline that failed for 2.1.4 release.
securesystemslib dependency more strictly to prevent future breakage (in 2.1.4)Full Changelog: https://github.com/sigstore/sigstore-python/compare/v2.1.4...v2.1.5
Loosened a version constraint on the sigstore-protobuf-specs dependency, to ease use in testing environments
sigstore-protobuf-specs dependency,
to ease use in testing environments
(#943)This is a corrective release for 2.1.1.
This is a corrective release for 2.1.1.
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v2.1.1...v2.1.2
Update pinned requirements for v2.0.1 by @github-actions in https://github.com/sigstore/sigstore-python/pull/800
ruff format by @woodruffw in https://github.com/sigstore/sigstore-python/pull/811{input}.sigstore.json by default by @woodruffw in https://github.com/sigstore/sigstore-python/pull/820Full Changelog: https://github.com/sigstore/sigstore-python/compare/v2.0.1...v2.1.0
CLI: When using --certificate-chain, read as bytes instead of str as expected by the underlying API
--certificate-chain, read as bytes instead of str
as expected by the underlying API (#796)Trust root configuration now assumes that the TUF repository contains a trust bundle, rather than falling back to deprecated individual targets
CLI: sigstore sign and sigstore get-identity-token now support the
--oauth-force-oob option; which has the same behavior as the
preexisting SIGSTORE_OAUTH_FORCE_OOB environment variable
(#667)
Version 0.2 of the Sigstore bundle format is now supported
(#705)
API addition: VerificationMaterials.to_bundle() is a new public API for
producing a standard Sigstore bundle from sigstore-python's internal
representation (#719)
API addition: New method sign.SigningResult.to_bundle() allows signing
applications to serialize to the bundle format that is already usable in
verification with verify.VerificationMaterials.from_bundle()
(#765)
sigstore verify now performs additional verification of Rekor's inclusion
proofs by cross-checking them against signed checkpoints
(#634)
A cached copy of the trust bundle is now included with the distribution (#611)
Stopped emitting .sig and .crt signing outputs by default in sigstore sign.
Sigstore bundles are now preferred
(#614)
Trust root configuration now assumes that the TUF repository contains a trust bundle, rather than falling back to deprecated individual targets (#626)
API change: the sigstore.oidc.IdentityToken API has been stabilized as
a wrapper for OIDC tokens
(#635)
API change: Signer.sign now takes a sigstore.oidc.IdentityToken for
its identity argument, rather than a "raw" OIDC token
(#635)
API change: Issuer.identity_token now returns a
sigstore.oidc.IdentityToken, rather than a "raw" OIDC token
(#635)
sigstore verify is not longer a backwards-compatible alias for
sigstore verify identity, as it was during the 1.0 release series
(#642)
API change: the Signer API has been broken up into SigningContext
and Signer, allowing a SigningContext to create individual Signer
instances that correspond to a single IdentityToken. This new API
also enables ephemeral key and certificate reuse across multiple inputs,
reducing the number of cryptographic operations and network roundtrips
required when signing more than one input
(#645)
sigstore sign now uses an ephemeral P-256 keypair, rather than P-384
(#662)
API change: RekorClientError does not try to always parse response
content as JSON
(#694)
API change: LogEntry.inclusion_promise can now be None, but only
if LogEntry.inclusion_proof is not None
(#705)
sigstore-python's minimum supported Python version is now 3.8
(#745)
Fixed a case where sigstore verify would fail to verify an otherwise valid
inclusion proof due to an incorrect timerange check
(#633)
Removed an unnecessary and backwards-incompatible parameter from the
sigstore.oidc.detect_credential API
(#641)
Fixed a case where sigstore sign (and sigstore verify) could fail while
using a private instance due to a missing due to a missing ExtendedKeyUsage
in the CA. We now enforce the fact that the TBSPrecertificate signer must be
a valid CA (#658)
Fixed a case where identity token retrieval would produce an unhelpful error message (#767)
build(deps-dev): update ruff requirement from <0.0.279 to <0.0.281 by @dependabot in https://github.com/sigstore/sigstore-python/pull/714
.sigstore bundles by @jleightcap in https://github.com/sigstore/sigstore-python/pull/721--upgrade to pip-compile in pin-requirements.yml by @di in https://github.com/sigstore/sigstore-python/pull/744pin-requirements.yml to use latest tag as default by @di in https://github.com/sigstore/sigstore-python/pull/748pin-requirements.yml by @di in https://github.com/sigstore/sigstore-python/pull/749Full Changelog: https://github.com/sigstore/sigstore-python/compare/v2.0.0rc2...v2.0.0rc3
build(deps-dev): update ruff requirement from <0.0.275 to <0.0.276 by @dependabot in https://github.com/sigstore/sigstore-python/pull/686
sigstore-conformance to 0.0.5 by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/684Full Changelog: https://github.com/sigstore/sigstore-python/compare/v2.0.0rc1...v2.0.0rc2
CHANGELOG: fix link by @woodruffw in https://github.com/sigstore/sigstore-python/pull/622
--output-directory by @tnytown in https://github.com/sigstore/sigstore-python/pull/627id-token: write permission by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/638detect_credential signature by @woodruffw in https://github.com/sigstore/sigstore-python/pull/641--oauth-force-oob CLI option by @laurentsimon in https://github.com/sigstore/sigstore-python/pull/667Full Changelog: https://github.com/sigstore/sigstore-python/compare/v1.1.2...v2.0.0rc1
Updated the staging-root.json for recent changes to the Sigstore staging instance
MyPy 1.1, fixes by @woodruffw in https://github.com/sigstore/sigstore-python/pull/530
TrustUpdater basic logging by @jleightcap in https://github.com/sigstore/sigstore-python/pull/518pydantic aliases in constructor to avoid mypy plugin bug by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/536id by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/535TrustUpdater error handling by @tnytown in https://github.com/sigstore/sigstore-python/pull/525requests by @tnytown in https://github.com/sigstore/sigstore-python/pull/541Full Changelog: https://github.com/sigstore/sigstore-python/compare/v1.1.1...v1.1.2rc1
NewTypes for clearer encoding types by @emilejbm in https://github.com/sigstore/sigstore-python/pull/474
Keyring abstraction by @jleightcap in https://github.com/sigstore/sigstore-python/pull/458custom field by @di in https://github.com/sigstore/sigstore-python/pull/522requirements.txt file by @di in https://github.com/sigstore/sigstore-python/pull/521.sig, .crt) + .sigstore by @jleightcap in https://github.com/sigstore/sigstore-python/pull/517Full Changelog: https://github.com/sigstore/sigstore-python/compare/v1.1.0...v1.1.1
NewTypes for clearer encoding types by @emilejbm in https://github.com/sigstore/sigstore-python/pull/474
Keyring abstraction by @jleightcap in https://github.com/sigstore/sigstore-python/pull/458custom field by @di in https://github.com/sigstore/sigstore-python/pull/522requirements.txt file by @di in https://github.com/sigstore/sigstore-python/pull/521.sig, .crt) + .sigstore by @jleightcap in https://github.com/sigstore/sigstore-python/pull/517Full Changelog: https://github.com/sigstore/sigstore-python/compare/v1.1.0...v1.1.1rc1
sigstore sign now supports Sigstore bundles, which encapsulate the same state as the default {input}.crt, {input}.sig, and {input}.rekor files combine
sigstore sign now supports Sigstore bundles, which encapsulate the same
state as the default {input}.crt, {input}.sig, and {input}.rekor
files combined. The default output for the Sigstore bundle is
{input}.sigstore; this can be disabled with --no-bundle or changed with
--bundle <FILE>
(#465)
sigstore verify now supports Sigstore bundles. By default, sigstore looks
for an {input}.sigstore; this can be changed with --bundle <FILE> or the
legacy method of verification can be used instead via the --signature and
--certificate flags
(#478)
sigstore verify identity and sigstore verify github now support the
--offline flag, which tells sigstore to do offline transparency log
entry verification. This option replaces the unstable
--require-rekor-offline option, which has been removed
(#478)
pyOpenSSL to >= 23.0.0 to prevent
a runtime error caused by incompatible earlier versions
(#448)--rekor-bundle and --require-rekor-offline have been removed entirely,
as their functionality have been wholly supplanted by Sigstore bundle support
and the new sigstore verify --offline flag
(#478)sigstore.rekor is now sigstore.transparency, and its constituent APIs have been renamed to removed implementation detail references
sigstore.rekor is now sigstore.transparency, and its constituent APIs
have been renamed to removed implementation detail references
(#402)
sigstore.transparency.RekorEntryMissing is now LogEntryMissing
(#414)
Nothing published for this version
sigstore verify is unchanged, but will be marked deprecated in a future stable version of sigstore-python
sigstore now supports the -v/--verbose flag as an alternative to
SIGSTORE_LOGLEVEL for debug logging
(#372)
The sigstore verify identity has been added, and is functionally
equivalent to the existing sigstore verify subcommand.
sigstore verify is unchanged, but will be marked deprecated in a future
stable version of sigstore-python
(#379)
sigstore now has a public, importable Python API! You can find its
documentation here
(#383)
sigstore --staging is now the intended way to request Sigstore's staging
instance, rather than per-subcommand options like sigstore sign --staging.
The latter is unchanged, but will be marked deprecated in a future stable
version of sigstore-python
(#383)
The per-subcommand options --rekor-url and --rekor-root-pubkey have been
moved to the top-level sigstore command. Their subcommand forms are unchanged
and will continue to work, but will be marked deprecated in a future stable
version of sigstore-python
(#381)
sigstore verify github has been added, allowing for verification of
GitHub-specific claims within given certificate(s)
(#381)
A series of Python 3.11 deprecation warnings were eliminated
sigstore verify now supports --certificate-chain and --rekor-url
during verification. Ordinary uses (i.e. the default or --staging)
are not affected (#323)sigstore sign and sigstore verify now stream their input, rather than
consuming it into a single buffer
(#329)
A series of Python 3.11 deprecation warnings were eliminated (#341)
The "splash" page presented to users during the OAuth flow has been updated
to reflect the user-friendly page added to cosign
(#356)
sigstore now uses TUF to retrieve its trust material for Fulcio and Rekor,
replacing the material that was previously baked into sigstore._store
(#351)
sigstore: 0.8.3 by @woodruffw in https://github.com/sigstore/sigstore-python/pull/317
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.8.2...v0.8.3
build(deps): bump sigstore from 0.6.7 to 0.6.8 in /install by @dependabot in https://github.com/sigstore/sigstore-python/pull/285
--cert-identity by @woodruffw in https://github.com/sigstore/sigstore-python/pull/289Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.8...v0.7.0
fix deprecated set-output by @bobcallaway in https://github.com/sigstore/sigstore-python/pull/270
ambient_oidc marker by @woodruffw in https://github.com/sigstore/sigstore-python/pull/259Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.7...v0.6.8
ci, Makefile: make check-readme a make target by @woodruffw in https://github.com/sigstore/sigstore-python/pull/233
check-readme a make target by @woodruffw in https://github.com/sigstore/sigstore-python/pull/233Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.6...v0.6.7
build(deps): bump sigstore from 0.6.4 to 0.6.5 in /install by @dependabot in https://github.com/sigstore/sigstore-python/pull/220
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.5...v0.6.6
build(deps): bump cryptography from 37.0.4 to 38.0.1 in /install by @dependabot in https://github.com/sigstore/sigstore-python/pull/203
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.4...v0.6.5
build(deps): bump sigstore from 0.6.2 to 0.6.3 in /install by @dependabot in https://github.com/sigstore/sigstore-python/pull/181
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.3...v0.6.4
oauth: use a context manager for the server's thread by @woodruffw in https://github.com/sigstore/sigstore-python/pull/140
cryptography to >= 3.1 to avoid incompatibilities by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/147--output flag by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/148sigstore-python GitHub Action by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/154--signature and --certificate aliases for the --output-{signature,certificate} flags by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/153lint exit non-zero with unstaged changes by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/169X509Store for each verify call by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/174Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.2...v0.6.3
build(deps): bump sigstore from 0.5.1 to 0.6.1 in /install by @dependabot in https://github.com/sigstore/sigstore-python/pull/134
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.1...v0.6.2
cli: fix --output-signature and --output-certificate by @woodruffw in https://github.com/sigstore/sigstore-python/pull/133
--output-signature and --output-certificate by @woodruffw in https://github.com/sigstore/sigstore-python/pull/133Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.6.0...v0.6.1
Add a requirements file w/ hashes, and additional instructions for installing by @di in https://github.com/sigstore/sigstore-python/pull/114
--cert-oidc-issuer flag by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/112Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.5.0...v0.5.1
Nothing published for this version
Nothing published for this version
_internal/fulcio: refactor SCT model by @woodruffw in https://github.com/sigstore/sigstore-python/pull/94
--output-signature and --output-certificate by @woodruffw in https://github.com/sigstore/sigstore-python/pull/101--fulcio-url and --rekor-url by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/103--staging convenience flag by @tetsuo-cpp in https://github.com/sigstore/sigstore-python/pull/104Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.4.2...v0.5.0
treewide: ratchet down typing, move mypy config to pyproject by @woodruffw in https://github.com/sigstore/sigstore-python/pull/85
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.4.1...v0.4.2
sigstore, README: add --version flag by @woodruffw in https://github.com/sigstore/sigstore-python/pull/79
--version flag by @woodruffw in https://github.com/sigstore/sigstore-python/pull/79Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.4.0...v0.4.1
cli: add a flag for disabling ambient OIDC detection by @woodruffw in https://github.com/sigstore/sigstore-python/pull/68
Full Changelog: https://github.com/sigstore/sigstore-python/compare/v0.3.1...v0.4.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →