Auto Updates

Tablen includes an automatic update system to keep the application current with the latest features, improvements, and security fixes.

Update Service

The Update Service manages the entire update lifecycle:

• Checking for available updates
• Downloading update packages
• Installing updates
• Notifying the user

Update Settings

Access update settings in Settings > Updates:

Automatic Update Checks

• Enable or disable automatic checking for updates
• When enabled, Tablen checks for updates periodically
• Manual check is always available via the "Check for Updates" button

Update Notifications

• When an update is available, a notification is shown
• The notification includes the new version number
• You can choose to update now or later

Update Process

Checking for Updates

1. Tablen contacts the update server
2. Compares the current version with the latest available
3. If a newer version exists, the update information is retrieved

Reviewing the Update

• View the version number of the available update
• Read the release notes for the new version
• Decide whether to install now or postpone

Installing Updates

1. Click "Update Now" when prompted
2. The update package is downloaded
3. The application restarts with the new version
4. Your data, connections, and settings are preserved

Update Safety

Data Preservation

• All connections, passwords, queries, and settings are preserved during updates
• The update process does not modify user data files
• Plugin configurations remain intact

Rollback

• If an update fails, the previous version remains functional
• Update errors are reported to the user

Manual Updates

If automatic updates are disabled:

1. Go to Settings > Updates
2. Click "Check for Updates"
3. If an update is available, follow the installation prompts

Offline Behavior

• Update checks require an internet connection
• If offline, the check is silently skipped
• The next check occurs when connectivity is restored

Release Channel

Tablen uses the tablen CLI tool for managing releases:

• Stable releases are the default
• Release candidates may be available for testing
• Updates follow the semantic versioning scheme