Skip to main content

3.4.0 to 3.5.0

No special instructions are necessary to upgrade to v3.5.0. A few important changes are noted below for awareness.

caution

The merlin-server Java package was published in v3.5.0 only to satisfy a transient dependency of orchestration-utils. This module is not intended for public use, and will be removed or made private in a future version. Do not build against it directly.

Aerie persistence of command, channel, parameter dictionaries

This release changes Aerie's behavior when uploading command, channel and parameter dictionaries via the Dictionaries page. Previously, Aerie would parse the uploaded dictionary into an internal, minimal format, but would not save the raw file provided by the user. As of v3.5.0, we will also save the raw file to the Aerie filesystem by default when uploaded via the UI, so that it may be used by Actions in the Sequence Editor Workspace. This is optional, so if your dictionary files contain sensitive information that you do not want to persist in Aerie, you should uncheck the "Save Dictionary to the filesystem" checkbox when uploading your dictionary.

DB Migrations

Multiple DB migrations were added in this release. If you are upgrading from a past version and want to preserve your data, follow the instructions in the Database Migrations Guide to apply migrations after upgrading. Make sure to either pass the --all flag, or apply all migrations interactively.

Plan Model Migration

Aerie now supports migrating a plan to a new mission model (not to be confused with DB migrations mentioned above). To perform a Plan Model Migration, first upload a new mission model via the Models page. Go to the Plans page and select your plan, and then click the Migrate button (arrows icon) next to the name of the plan in the left-side panel to choose the new Model to migrate to.