ChatWalaʻau v0.117.4

This release fixes Archive in the chat list. On any deployment that configures a session directory, archiving a chat failed with an unexplained error — and the interface said nothing at all about it.

✅ No breaking changes. With the default session directory the on-disk layout is unchanged. If you set SESSIONS_DIR, see the note under the first item.

Highlights

Fixed: Archive failed with an unexplained error when SESSIONS_DIR is set (v0.117.4)

• The archive folder was a fixed .archived next to the process working directory, instead of next to the session directory you configured. With the default setting the two are the same place, which is why this only appeared on a configured deployment.
• Two things went wrong there. Archived chats landed outside the session store, so a backup of that volume did not carry them. And when the session store is a mounted volume, the archive was on a different filesystem — a move across filesystems is not permitted, so every Archive click failed with HTTP 500.
• The archive folder is now derived from your session directory, and the move works across filesystems.
• If you set SESSIONS_DIR: new archives go to .archived/ next to it. Anything archived by an earlier version is in .archived/ next to the server's working directory — move those files across to keep your archive in one place.

Fixed: a failed archive gave no feedback (v0.117.4)

• The interface only handled success, so a failure left the chat sitting in the list as if nothing had been clicked. The single symptom was a 500 in the browser console.
• The sidebar now shows the server's reason: which directory it could not use, that the location follows the SESSIONS_DIR setting, and what to fix — typically a read-only or unmounted volume. It also states plainly that the chat was not archived and is still in your list.
• Verified end to end in the browser against a deliberately broken archive location.

Fixed: attachment problems no longer fail an archive that already succeeded (v0.117.4)

• Moving a chat's attachments happens after the chat itself is archived. If that step failed, the whole request reported an error for something that had in fact happened.
• The attachments are now left in place and a warning is logged, and the archive is reported as the success it was.

Included in this release

This release includes implementation work from:

• v0.117.4 through v0.117.4

Notes

• Internal design management content and architecture control artifacts are intentionally omitted from this release note.

Installation

See the repository README for setup and usage instructions.

Version

• Release version: 0.117.4
• Previous release: 0.117.3