ragleap-core v0.13.2 was published on 2026-11-10. It is audit and sign-in hardening: everything new is read-only or opt-in, except the sign-in rate limit, which is on by default for the single sign-on (itself off by default). Source: the v0.13.2 release notes.
What can I filter in the audit log?
GET /audit can now be filtered and paged by method, path (starts with), status, since, until (ISO 8601) and before_id (#1306). Calls without these parameters behave as before.
How does audit retention work?
It is opt-in (#1318). Three settings, AUDIT_RETENTION_DAYS, ACTION_LOG_RETENTION_DAYS and AGENT_RUN_RETENTION_DAYS, default to empty or 0, which keeps everything; a value of 1 to 6 is refused. When a limit is set, the scheduler leader deletes older rows every 6 hours in small batches, and runs that are running or waiting for approval are never deleted. Each purge writes a retention_purge AUDIT line. Two new routes: GET /retention (admin) and POST /retention/purge (owner, dry run by default).
What is the request id in the logs?
The X-Request-ID of a call is now carried by the AUDIT log lines written while handling it, as request_id (#1319). LOG_REQUEST_ID=true puts it in every app log line; it is off by default.
What is the sign-in rate limit?
/auth/login and /auth/callback accept at most AUTH_SSO_MAX_PER_MINUTE requests per client and minute (default 30, range 1 to 10000), then answer 429; the callback redirects back with a message (#1325). The first refusal per client and minute writes a sso_rate_limited AUDIT line. Behind a reverse proxy, list it in TRUSTED_PROXIES, otherwise everyone behind it shares one counter. AUTH_THROTTLE=off switches it off.
What should I know before upgrading?
- No schema change and no new dependency. Rebuild and restart the app.
- All new settings are optional and default to the old behaviour, except the sign-in rate limit (on by default, generous).
- Deleting history removes evidence. Ship the AUDIT lines to a log store first, and choose the retention period with your own counsel. Nothing here makes an installation compliant with any law or standard.
What is not covered yet?
- The request id is not stored in the database rows.
- Lines written later in the background have no request id.
- Stored prompts are not redacted.
New guides: docs/audit-retention.md and docs/audit-log-lines.md; docs/single-sign-on.md now describes the rate limit. The release notes thank Paige Ortiz (CerTova AI) for the technical review that prompted the audit work, and everyone who tested and reported. More: our release page and the roadmap.