v0.2.29

Doca 0.2.29 — AI conversation history and deletion fixes

简体中文

New AI turns save the original question and owned attachment information before file validation, model initialization and attachment recognition. If setup fails, reopening or refreshing the conversation still shows the question, attachment and task failure. An existing saved message and its context remain intact when an attempt resumes.

The welcome screen no longer appears below queued or running task progress when messages have not arrived. Loading an existing conversation suppresses the welcome screen; starting a new conversation restores it. Render caching includes the selected conversation ID.

Conversation deletion now shows errors inside the confirmation dialog and supports retry. Conversations with active tasks offer an explicit Stop task action before a separate deletion confirmation. The server continues to reject deletion while tasks are queued, running or awaiting approval, including when their state changes after opening the dialog. Stopping tasks does not automatically delete a conversation. Chinese and English prompts are included.

No database structure, stored format or historical-message recovery is introduced. Existing missing message records are not reconstructed or rewritten. Existing historical message readers, retry defaults and session-file cleanup rules are unchanged. Preserve databases, attachments, configuration and master keys, and update server and Web together. The 0.2.28 upgrade requirements still apply. See the verification record for scope and evidence.

GitHub Release assets and native Linux amd64/arm64 Docker Hub images are the publication targets. Fresh installations can use doca-compose-v0.2.29.yaml; existing installations retain their deployment identity and volumes. Publishing does not deploy a running site. The browser extension remains version 0.2.11.

Web assets are attached as doca-web-assets-v0.2.29.tar.gz.
Extract it and publish the assets directory unchanged.
Set DOCA_ASSET_BASE to the HTTPS prefix that contains that assets directory, with no trailing slash.

Fresh installations can use the attached doca-compose-v0.2.29.yaml: edit the origin and generated master key, then run docker compose up -d. Administrator initialization is built into the image. A SHA-256 checksum is attached. Existing installations must preserve their project, volumes and key.

Image-only deployment files and initialization instructions are attached as doca-deploy-v0.2.29.tar.gz with a SHA-256 checksum.
Transfer this bundle to servers without GitHub access; no source checkout is needed.
The container image is separate. Pull the matching smartdoca/doca image or transfer it with docker save/load.