Ferriskey

Release notes

How Ferriskey has been taking shape, release after release.

A curated timeline of stable Ferriskey releases, condensed from the public GitHub history into product-level notes.

Based on the public release history of ferriskey/ferriskey on GitHub.

GitHub release Back to homepage

Stable release timeline

Newest first. Milestone releases ship new capabilities; patch releases are quick fixes to an existing line.

v0.7.1 July 3, 2026
Patch release Latest release

Nginx packaging fix for the 0.7 line

A small patch that cherry-picks an Nginx configuration fix into the 0.7 release line so the packaged web application image keeps serving correctly.

  • Cherry-picks the Nginx fix into 0.7.1 so the packaged webapp is served correctly in the shipped image.
  • Bumps workspace, Helm chart, and operator chart versions together to keep artifacts aligned.
  • Keeps the 0.7 branch production-ready without requiring a larger upgrade.

A narrow follow-up to 0.7.0 that ensures the release ships cleanly in containerized environments.

GitHub release Compare changes
v0.7.0 June 30, 2026
Milestone release

Device authorization flow and the portal theming builder

FerrisKey 0.7.0 brings the OAuth 2.0 Device Authorization Grant (RFC 8628) end to end and a full portal theming builder, letting teams onboard input-constrained devices and fully brand their login experience.

  • Implements the complete OAuth 2.0 Device Authorization Flow (RFC 8628): device authorization endpoint, device_code token grant, verification page, and CIAM console configuration.
  • Ships a portal theming builder with per-page layouts, design tokens, live preview, and an iframe-based editor to fully customize the hosted login portal.
  • Adds CIAM application management, resume-OAuth-after-password-reset, basic auth support, and several OIDC discovery and nonce compliance fixes.

With operational control settled in 0.6, the 0.7 line turns toward developer-facing protocol coverage and end-user branding — making FerrisKey both more standards-complete and more customizable.

GitHub release Compare changes
v0.6.1 June 8, 2026
Patch release

Authentication flow fixes and passkey configuration polish

A patch release for the 0.6 line that bundles a set of authentication-flow fixes across passkey configuration, OTP challenge handling, identity-provider brokering, and redirect URI handling.

  • Refines the passkey configuration experience and hardens the OTP challenge flow on the login journey.
  • Fixes the GitHub identity-provider broker login flow and cleans up redirect URI handling.
  • Smooths the login and post-authentication callback path across the frontend.

Right after 0.6.0's operational features, this patch tightens the day-to-day authentication experience before the larger 0.7 work.

GitHub release Compare changes
v0.6.0 May 6, 2026
Milestone release

Maintenance mode, user attributes, and OpenTelemetry tracing

FerrisKey 0.6.0 introduces two major platform capabilities — a built-in maintenance mode and extensible user attributes — alongside full OpenTelemetry tracing support for production observability.

  • Ships a first-class maintenance mode across the full stack, letting administrators halt user-facing operations gracefully during upgrades or incidents while retaining admin access.
  • Adds user attributes support so realms can store arbitrary key-value metadata on users and propagate them into tokens via protocol mappers.
  • Integrates OpenTelemetry tracing and OTLP log bridge for seamless compatibility with observability stacks such as Grafana Tempo and Jaeger.

Building on the passwordless and multi-tenant foundations of 0.5.0, this release shifts focus to operational control and extensibility — giving platform teams the tools to manage identity infrastructure with greater confidence.

GitHub release
v0.5.0 April 12, 2026
Milestone release

Passwordless authentication, organizations, and email theming

Ferriskey 0.5.0 moves the product beyond core IAM administration with native passwordless sign-in, multi-tenant organization management, and customizable transactional emails.

  • Adds native WebAuthn passkeys for passwordless authentication without heavy external infrastructure.
  • Introduces Magic Link sign-in for teams that want a simpler passwordless user experience.
  • Ships organizations and email builder theming so tenants and transactional emails can be managed directly from Ferriskey.

After the 0.4 line focused on observability, recovery, and token control, 0.5.0 turns that foundation into a more complete end-user and multi-tenant experience.

GitHub release Compare changes
v0.4.3 March 24, 2026
Patch release

Authentication URL hardening and release alignment

A focused patch that hardens authentication and registration URL generation, especially when Ferriskey runs behind a root path or a webapp URL with trailing slashes.

  • Normalizes login URL construction to avoid double slashes in authentication redirects.
  • Applies root-path aware base URLs to authenticate, registration, and token exchange handlers.
  • Bumps workspace and Helm chart versions together so the shipped artifacts stay aligned.

This closes the 0.4 line with a practical production fix: cleaner redirects, safer URL composition, and properly aligned release metadata.

GitHub release Compare changes
v0.4.2 March 13, 2026
Patch release

Dockerfile and Nginx packaging fixes

A packaging-focused patch release that fixes the delivery layer around the web application, with corrections in the Docker entrypoint, Dockerfile flow, and Nginx configuration.

  • Fixes the Dockerfile path so the packaged web application boots with the expected assets.
  • Corrects the container entrypoint behavior in the release build.
  • Updates Nginx configuration so the shipped image serves the app correctly.

It is a narrow release, but an important one: it turns the 0.4 branch into something easier to ship and verify in containers.

GitHub release Compare changes
v0.4.1 March 12, 2026
Patch release

Authentication callback flow refinement

A patch release centered on the authentication callback path, tightening refresh-token behavior and smoothing the post-login handoff.

  • Fixes the authentication callback flow after the broader 0.4.0 changes.
  • Adjusts refresh-token logic so sign-in completion behaves more predictably.
  • Stabilizes the handoff between the login journey and token lifecycle.

This patch serves as the functional correction right after 0.4.0 before the packaging fixes that landed in 0.4.2.

GitHub release Compare changes
v0.4.0 March 12, 2026
Milestone release

Client scopes, Compass observability, and account recovery foundations

Version 0.4.0 is a major step forward for platform teams: token shaping improves, authentication flows become observable, and user recovery starts to land as a complete subsystem.

  • Introduces client scopes, mappings, migrations, and API support for better token composition.
  • Launches Compass runtime, database layer, API endpoints, and UI to inspect authentication flows.
  • Adds password reset and SMTP management building blocks, including UI and infrastructure.

Once federation was established in 0.3.0, the next logical move was to improve policy control, visibility, and recovery across the sign-in journey.

GitHub release Compare changes
v0.3.0 February 2, 2026
Milestone release

Federation becomes real

Ferriskey expands beyond local identity management with federation primitives, social login, LDAP support, and SSO endpoints.

  • Adds the Abyss federation module and user federation entities and migrations.
  • Ships social auth APIs, LDAP provider CRUD, sync and connection test endpoints.
  • Improves login UX, error detail quality, and permissions hydration in the app.

At this point the project stops being only an internal IAM console and starts addressing real-world enterprise identity integration problems.

GitHub release Compare changes
v0.2.1 January 16, 2026
Patch release

Maintenance patch for the 0.2 line

A small release that backports the necessary fixes to keep the 0.2 branch versioned and consumable while larger federation work continues on main.

  • Cherry-picks targeted fixes from main into the 0.2 release line.
  • Corrects release versioning before the next milestone.
  • Keeps existing adopters on a stable branch without forcing a larger upgrade.

It is a short stop on the timeline, but it shows the project already treating release management as part of the product.

GitHub release Compare changes
v0.2.0 December 30, 2025
Milestone release

Operations, webhooks, and admin surface expansion

Ferriskey broadens its operator story with webhooks, required actions, stronger admin pages, and the first serious steps toward event-driven integrations.

  • Introduces webhook notifications and required actions in the authentication journey.
  • Expands admin UX with realm settings, login settings, IdP overview, and UI polish across clients and roles.
  • Lays groundwork for SeaWatch and strengthens deployment support with TLS and Docker improvements.

From here the roadmap opens up: not just authenticating users, but integrating identity events into the rest of the platform.

GitHub release Compare changes
v0.1.1 August 11, 2025
Patch release

First post-launch hardening pass

The first patch release focuses on correctness and release hygiene right after the initial public milestone.

  • Fixes session cookie handling to make authentication flows safer.
  • Corrects Docker Compose execution context issues.
  • Cleans up the Helm release workflow so tags are published more predictably.

This is where the team starts closing the gap between a fast-moving launch and a project people can trust to upgrade.

GitHub release Compare changes
v0.1.0 August 7, 2025
Milestone release

The first public Ferriskey baseline

The first stable release establishes the platform core: realms, clients, users, roles, OpenID endpoints, admin UI, packaging, and deployment tooling.

  • Delivers the foundational IAM surface: realms, clients, roles, permissions, users, and authentication endpoints.
  • Ships the first admin portal flows, including login, client management, role management, and user management.
  • Adds Helm, operator, Docker, metrics, and documentation so Ferriskey can be evaluated as a real platform.
GitHub release