Releases and compatibility
Prepare for product updates and understand which information to record before an upgrade.
CogLake updates can change stored data, processing behavior, and search. Administrators should use the complete tested release supplied for their installation rather than updating individual components independently.
Before an update
- Read the release notes supplied with the target version.
- Create and verify an encrypted backup.
- Record the current product version and any model or index versions shown in diagnostics.
- Confirm available storage and a maintenance window.
- Run the supplied non-destructive preflight when one accompanies the update.
Compatibility
Keep all supplied components on the same release. Stored-data upgrades run forward; restoring an older product release against newer data is not assumed to be safe. A rollback therefore uses the prior release together with the backup created before the upgrade.
Search indexes can be rebuilt from source data when required. Preserve compatible indexes when the release notes allow it to avoid unnecessary model cost and processing time.
Support information
When reporting an update issue, include the source and target versions, preflight output, migration status, and a support bundle. Do not include connector secrets, bearer tokens, or decrypted backup material.