RELEASE HISTORY

Changelog

What changed, when and why. We always list the changes that affect security.

Unreleased

Features in active development.

Added

Planned

v3.1.3

not yet tagged; the tag goes on the merge commit before the site rollout

The examples on the home page are calm and real: no badge, no stamps and no drawn fake screens, just one heading, one sentence and one button each. The installer clones the v3.1.3 tag. The full list is in CHANGELOG.md.

v3.1.2

not yet tagged; the tag goes on the merge commit before the site rollout

The public transparency log tells the truth about itself: the mirror of other relays only holds tree heads from pinned keys, the 39 entries from April 2026 get their proof and tree hash from the current tree, and a customer can check a receipt himself. The installer clones the v3.1.2 tag. The full list is in CHANGELOG.md.

v3.1.1

not yet tagged; the tag goes on the merge commit before the site rollout

Repair round after 3.1.0: what a buyer reads around paying matches what he gets, the deploy checks the host hardening /dpa promises, and the installer clones the v3.1.1 tag. The full list is in CHANGELOG.md.

v3.1.0

running in production, not yet tagged

ParaSign as a product, security findings fixed and payment through Mollie. The full list is in CHANGELOG.md.

Security

Added

Changed

Removed

v3.0.0

27 May 2026

One version number for the whole project, and the post-quantum building blocks in their own library.

Changed

Fixed

v0.9.0-beta

20 April 2026

Admin panel hardening + email overhaul + TOTP security sprint.

Added

Changed

Fixed

Security

v0.9.0-beta

19 April 2026

Enterprise readiness sprint. Admin panel redesign + security audit.

Added

Changed

Fixed

Security