migrate

To upgrade a Starlake project, execute the migrate command to automatically update configuration files, pipelines, dependencies, schemas, and YAML definitions to the latest compatible core version with minimal manual intervention.

A Starlake version migration updates project configuration files, pipeline definitions, schemas, YAML files, and plugin references, while reconciling version-specific changes to validate compatibility with the target runtime.

You need to migrate your Starlake project configuration when upgrading to the newest core version to handle breaking changes, deprecations, and compatibility issues that would otherwise cause runtime errors.

Yes, the migration process validates compatibility with the target Starlake core version and highlights necessary migrations across schemas, YAML definitions, and plugin references before applying the changes.

The best way to handle breaking changes during a Starlake upgrade is to run the automated migration tool, which reconciles version-specific changes across configuration and pipelines to prevent errors.

Your Starlake project configuration may not work after a version upgrade due to unresolved deprecations or breaking changes in schemas, YAML definitions, and plugin references that require automated migration.