Skip to content

Prepare 4.4 release #1813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jku merged 1 commit into from
Jul 6, 2026
Merged

Prepare 4.4 release #1813

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,19 @@ All versions prior to 0.9.0 are untracked.

## [Unreleased]

## [4.4.0]

### Changed

* `sigstore` no longer limits the upper-bound of `cryptography` in order
to be less disruptive to downstream integrators.
([#1811](https://github.com/sigstore/sigstore-python/pull/1811))

### Fixed

* Fixed generation of invalid CSRs when the identity is not ASCII (for
example a GitHub Actions `sub` claim containing a non-ASCII environment
name). The identity was embedded as an ASCII-only IA5String email
attribute, producing malformed DER that Fulcio rejected with HTTP 400.
The CSR subject is unused by Fulcio, so it is now omitted entirely
name). The CSR subject is unused by Fulcio, so it is now omitted entirely
([#1507](https://github.com/sigstore/sigstore-python/issues/1507))

## [4.3.0]
Expand Down
2 changes: 1 addition & 1 deletion sigstore/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,4 +25,4 @@
* `sigstore.sign`: creation of Sigstore signatures
"""

__version__ = "4.3.0"
__version__ = "4.4.0"
Loading