# Upgrade checklist

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

Upstream release notes describe changes to the underlying engine and application. Sydekyks also changes branding and independently owned assistant modules. Keep both change sets attached to the actual deployed revision.

The latest published application release is Sydekyks 1.0.6. Its release log (https://www.sydekyks.com/releases/#v1.0.6) covers free use of every available feature, without activation, trials or license expiry. Old license records are ignored. Custom clients must stop calling /v1/sydekyks-license/* or waiting for sydekyks:license-required. Back up the database, file storage, encryption/JWT keys and environment, then update every app and worker together. Account permissions and workspace isolation remain enforced. Check a representative mission before resuming normal work.

Release preparation included a backed-up 1.0.4 upgrade and isolated PostgreSQL restoration on a development candidate. The final image received build and startup checks; broader application and visual testing was deferred to future CI. These checks do not replace a recovery rehearsal for your own deployment. See backup and recovery (https://docs.sydekyks.com/install/configure-operate/rollback).

## ​Before upgrading

- Record the current image tag, source revision and edition.

- Read the upstream compatibility notes between that revision and the intended target.

- Review Sydekyks-specific changes and configuration.

- Back up the database, file storage and encryption/configuration secrets.

- Restore the backup into an isolated staging environment.

- Apply the target image there and check migrations and representative automations.

## ​Check the behavior

Test triggers, connection callbacks, variables, tables, retries, waiting runs, file storage and WebSockets. Reconcile any renamed or removed environment variable before restarting the live service.

## ​Rollback boundaries

A database migration may make a simple image rollback insufficient. Decide whether recovery requires a database restore before applying the update. Use backup and rollback (https://docs.sydekyks.com/install/configure-operate/rollback).

This guide does not instruct a Community deployment to switch to AP_EDITION=ee. Review the edition-specific migration history separately if the deployment plan ever changes.

The pinned upstream documentation (https://github.com/activepieces/activepieces/blob/ce23d047affdc0f6b4e42cc688a685569db9babe/docs/install/reference/breaking-changes.mdx) is retained as a compatibility source, not relabeled as a Sydekyks product release history.