Skip to content

Conversation

@wolfv
Copy link
Member

@wolfv wolfv commented Jan 16, 2026

🤖 New release

  • sigstore-types: 0.6.0 -> 0.6.1
  • sigstore-crypto: 0.6.0 -> 0.6.1
  • sigstore-merkle: 0.6.0 -> 0.6.1
  • sigstore-tsa: 0.6.0 -> 0.6.1
  • sigstore-trust-root: 0.6.0 -> 0.6.1
  • sigstore-cache: 0.6.0 -> 0.6.1
  • sigstore-rekor: 0.6.0 -> 0.6.1
  • sigstore-bundle: 0.6.0 -> 0.6.1
  • sigstore-oidc: 0.6.0 -> 0.6.1
  • sigstore-fulcio: 0.6.0 -> 0.6.1
  • sigstore-verify: 0.6.0 -> 0.6.1 (✓ API compatible changes)
  • sigstore-sign: 0.6.0 -> 0.6.1
Changelog

sigstore-types

0.6.0 - 2025-12-08

Other

  • improve types and add interop test workflow (#9)

sigstore-crypto

0.4.0 - 2025-11-28

Other

  • introduce new artifact api

sigstore-merkle

0.3.0 - 2025-11-28

Other

  • more cleanup of functions

sigstore-tsa

0.3.0 - 2025-11-28

Other

  • remove more types
  • remove certifactePem
  • improve sign / verify flow, add conda specific test
  • more cleanup of functions

sigstore-trust-root

0.5.0 - 2025-12-01

Added

  • Add SigningConfig support and V2 bundle fixes (#6)

sigstore-cache

0.3.0 - 2025-11-28

Fixed

  • fix clippy warnings

Other

  • add simple separation for cache domains
  • add sigstore-cache

sigstore-rekor

0.5.0 - 2025-12-01

Added

  • Add SigningConfig support and V2 bundle fixes (#6)

sigstore-bundle

0.6.0 - 2025-12-08

Added

  • add fuzzing tests (#13)

Other

  • improve types and add interop test workflow (#9)

sigstore-oidc

0.2.0 - 2025-11-27

Other

  • remove duplicated types, add license and readme files

sigstore-fulcio

0.3.0 - 2025-11-28

Fixed

  • fix clippy warnings

Other

  • add sigstore-cache
  • remove more types
  • encode more certificates properly

sigstore-verify

0.6.1 - 2026-01-24

Fixed

  • (conformance) add verification with key (#41)

sigstore-sign

0.6.0 - 2025-12-08

Other

  • improve types and add interop test workflow (#9)


This PR was generated with release-plz.

@wolfv wolfv force-pushed the release-plz-2026-01-16T23-21-04Z branch from db1effc to 4b1e7e1 Compare January 18, 2026 21:51
@wolfv wolfv force-pushed the release-plz-2026-01-16T23-21-04Z branch from 4b1e7e1 to d263b10 Compare January 24, 2026 07:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants