Appearance

Upgrading Frona involves pulling the latest code and rebuilding the containers.

Upgrading from v2026.9.0 to v2026.10.0 ​

  • Provider connections: Existing built-in provider keys remain valid. For multiple accounts, give each connection a handle and set its provider brand explicitly. Update model groups and their fallbacks to reference those handles. See Providers & Models.
  • OpenAI protocol default: OpenAI-branded connections now default to Responses, including unknown or manually entered model IDs. Set api: completions if your endpoint requires Chat Completions. Existing api: chat_completions values remain accepted.
  • Model settings: Check the protocol and settings for each group and fallback. Unsupported typed settings are rejected. Native request fields can be supplied through extra_params, except for conversation, tool, streaming, and structured-output fields managed by Frona.
  • Configuration saves: The UI preserves unrelated overrides and environment references. Reload settings if a save reports a revision conflict, and restart when prompted to activate saved configuration. Malformed or unreadable YAML is now a startup error.
  • Credentials: Newly saved provider keys and account tokens use encrypted managed storage in the database. Include the database, configuration, and encryption secret in your backup. Existing inline YAML keys remain supported.
  • Development containers: Rebuild with mise run container:dev:build to install Bacon and Kache. Host dev, dev:backend, and dev:frontend tasks have been removed; use mise run container:dev.

After upgrading, verify provider authentication, the primary model and fallback chain, and a credential-backed agent command. The About dialog includes the embedded source revision to help identify the running build.

Upgrade procedure ​

1. Back up your data ​

Always back up before upgrading. See Backups.

bash
docker compose stop frona
tar czf frona-backup-pre-upgrade.tar.gz data/ .env

2. Pull the latest code ​

bash
git pull origin main

3. Check for configuration changes ​

Review the changelog or diff for any new environment variables or changed defaults. Update your .env file if needed.

4. Rebuild and restart ​

bash
docker compose build
docker compose up -d

5. Verify ​

Check that all services are running:

bash
docker compose ps

Open the web interface and verify everything works as expected.

Rolling back ​

If something goes wrong:

  1. Stop the services: docker compose down
  2. Check out the previous version: git checkout <previous-commit>
  3. Restore your data backup if needed
  4. Run docker compose build, then docker compose up -d.

Database migrations ​

SurrealDB handles schema changes automatically in most cases. If a version requires a specific migration, it will be documented in the release notes.

Version pinning ​

If you want to pin to a specific version instead of tracking main, use git tags:

bash
git checkout v2026.10.0
docker compose build
docker compose up -d
Frona AI