Jeena
7c2a7a98e7
Simple local Docker update via existing update.sh script. Context file tells the classifier this is a single Docker instance, so database migration warnings aimed at multi-worker deployments are correctly classified as auto.
20 lines
1.6 KiB
Text
20 lines
1.6 KiB
Text
action: auto
|
|
reason: Database schema changes and long-running migration run automatically on startup for single-instance Docker deployments. The warnings about simultaneous updates only apply to multi-worker or load-balanced setups, which this is not.
|
|
---
|
|
> [!CAUTION]
|
|
> Database Migrations: This release includes database schema changes; we strongly recommend backing up your database and all associated data before upgrading in production environments. If you are running a multi-worker, multi-server, or load-balanced deployment, all instances must be updated simultaneously, rolling updates are not supported and will cause application failures due to schema incompatibility.
|
|
|
|
> [!WARNING]
|
|
> Long-Running Database Migration: This release includes a migration for the `chat_message` table that can take a significant amount of time to complete, especially in larger deployments with extensive chat histories. Please plan for adequate downtime and allow the migration to finish completely without interruption.
|
|
|
|
### New features
|
|
|
|
- Experimental support for Open Responses protocol
|
|
- Yandex search provider
|
|
- Custom password hints via PASSWORD_VALIDATION_HINT environment variable
|
|
- MCP custom SSL certificates support
|
|
|
|
### Important notes
|
|
|
|
- Database Migration Required — This release includes database schema changes; multi-worker, multi-server, or load-balanced deployments must update all instances simultaneously.
|
|
- Chat Message Table Migration — This release includes a new chat message table migration that can take a significant amount of time to complete in larger deployments with extensive chat histories.
|