Raytha v2.0.1: fixes for routes, functions, and sign-in

A patch on 2.0.0: route paths, Raytha Functions, SSO, list views, and email. There is no database migration.

Released October 3, 2026.

Raytha 2.0.1 is a patch on 2.0.0. There is no database migration.

Docker: raythahq/raytha:2.0.1 (also latest).

What's new

Login says which field is missing, and changing a password to the same value is rejected.
Audit log date filters no longer crash, and dates are compared in UTC.
Sorting a content list by template no longer crashes.
Read-only queries no longer track entities, and they use async database calls.
Date filters accept ISO dates only. A value written in the organization's display format is rejected instead of being parsed.
The webhook form groups events, explains what a webhook does, and can send a test delivery.
Route paths may contain a dot in any segment, and a path may start with /.well-known/. .. and other hidden segments are still rejected. An existing route may keep a reserved path.
SAML responses are decoded as UTF-8, so a non-ASCII name no longer fails the signature check.
RAYTHA_FUNCTIONS_MAX_ACTIVE=0 disables Raytha Functions.
.NET Math is exposed to functions as DotNetMath, so it no longer hides the JavaScript Math object.
Content item lists are compact, and the action column stays visible.
A public user receives the password-changed email.
Maintenance can send a test email to an address you type. An unset SMTP host is reported instead of being skipped.
A content item's template picker follows the active theme.
The themes list shows which theme is active.
The README documents the Raytha CLI.
An HTTP, background, or Liquid function receives its request as parsed JSON. The body is never spliced into the script. An empty body is null, and text that is not JSON stays a string.
An admin-only JWT or SAML scheme no longer creates a public user for an unknown email.
Raytha Functions cannot read JwtSecretKey or SamlCertificate. The admin API and Liquid templates are unchanged.