RagLeap
Blog

v0.13.5: old approvals expire, Discord requests with an old timestamp are refused, and connector credentials fail closed

ragleap-core v0.13.5 was published on 2026-11-17. It has three more hardening fixes that came out of the outside assessment of our approval and connector code by Aleksei Musienko (AMQIC), described in the v0.13.4 post. Upgrading switches nothing new on. Source: the v0.13.5 release notes, checked on 2026-11-18.

Do old approvals expire now?

Yes (#1455). A pending action that waited longer than APPROVAL_EXPIRY_HOURS (default 168, which is 7 days) is not run by a late approval. The person is told it expired, and it is logged. Rejecting an old one still works. 0 turns the limit off. Pending actions that are already older than 7 days are refused after this update.

How are Discord requests protected from replay?

A validly signed Discord request is accepted only within DISCORD_MAX_SKEW_SECONDS (default 300) of the server time, so a captured request cannot be replayed later (#1456). 0 turns it off. The server clock must be right, so use time sync.

What does "connector credentials fail closed" mean?

Without ADDON_ENCRYPTION_KEY, a connection string, API key or credential-looking header is refused instead of being stored in plain text. With a key, credential headers are stored encrypted. The Mongo connector now puts the user identifier into the filter as a plain value instead of splicing it into JSON text (#1462; S1-001 and S1-006 in the assessment). Rows stored earlier are not changed, and older plain header rows still read.

What should I know before upgrading?

  • No schema change and no setting you must set. File writing, deleting and sub-agents stay off.
  • Approvals older than 7 days are refused after the update. Set APPROVAL_EXPIRY_HOURS=0 to turn the limit off.
  • If you use connectors with credentials, set ADDON_ENCRYPTION_KEY first, or saving them is refused.

What is not tested or not covered?

Not tested yet: a real Discord server, a real MongoDB, and the dashboard text for an expired approval. The outside review of file writing (#800) has not happened. This is not a certification, and the release does not claim that every item of the assessment is closed.

The release notes thank Aleksei Musienko for the outside assessment and for the public security notes that gave us ideas. More: the page about the assessment, our release page and the roadmap.

Quick answers

How long can an approval wait in RagLeap Core?

By default 168 hours (7 days), set by APPROVAL_EXPIRY_HOURS. After that a late approval does not run the action, the person is told it expired, and it is logged. Rejecting still works, and 0 turns the limit off.

How does RagLeap protect Discord approvals from replay?

A validly signed Discord request is accepted only within DISCORD_MAX_SKEW_SECONDS of server time (default 300), so a captured request cannot be replayed later. 0 turns it off, and the server clock must be right.

Does RagLeap store connector credentials in plain text?

Not since v0.13.5. Without ADDON_ENCRYPTION_KEY a connection string, API key or credential-looking header is refused. With a key, credential headers are stored encrypted. Rows stored earlier are not changed.

Do I need to change a setting to upgrade to v0.13.5?

No setting is required and there is no schema change. If you use connectors with credentials, set ADDON_ENCRYPTION_KEY first. Approvals older than 7 days are refused after the update.

Back to the blog