v0.1.4

What's Changed

• Change embedded version naming on proto types in #329
• Bump tessera library to v0.2.0 beta release in #331
• organize protos into subdir rekor/v2 in #339

Docs

• Document required client changes for Rekor v2 in #255
• Update clients documentation with API changes in #330

Full Changelog: v0.1.3...v0.1.4

v0.1.3

What's Changed

• Fix HTTP connection for gRPC over TLS in #322
• Remove json_name from proto message fields in #323

Full Changelog: v0.1.2...v0.1.3

v0.1.2

What's Changed

• App: Log signing key public key on startup in #317
• Rename trillian-tessera library, bump to latest commit in #318
• use GCP-compatible structured logging in #300
• Split TLS flags into separate gRPC and HTTP flags in #319

Full Changelog: v0.1.1...v0.1.2

v0.1.1

What's Changed

The most significant change with v0.1.1 is to the CreateEntry API and what's stored in the log. An Entry now includes a kind (e.g. hashedrekord, dsse), version (e.g. 0.0.2) and spec to be compatible with Rekor v1's log entries.

Full Changelog: v0.1.0...v0.1.1

Rekor v2 alpha release

We are very excited to announce the alpha release of Rekor v2!

Rekor v2 is a redesigned and modernized Rekor, Sigstore's signature transparency log, transitioning its backend to a modern, tile-backed transparency log implementation to simplify maintenance and lower operational costs.

Read the blog post and README for more information.