Skip to main content

3.3.1 to 3.4.0

A new Upgrade Process guide was recently added to our documentation, please refer to that document for general upgrade instructions.

Database migrations​

Aerie v3.4.0 adds two new database migrations, please be sure to run the database migration script when upgrading if you want to preserve your data in Aerie v3.4.0.

Interface changes​

Some changes have been made to the API and database structure for constraint definitions and constraint runs, to support Procedural Constraints. The constraint_run table has been split into three tables: constraint_run, constraint_request, and constraint_result. The constraint_definition table has been updated to support JARs, and constraint specification tables have been updated to support invocations, arguments and priority. The Hasura action for running constraints now accepts an optional boolean force flag - if set to true, the Action will skip loading results from the cache - and its response body now includes the generated request id.

For full details about these changes, see the Pull Request Procedural Constraints Action/Database Support #1596

New Features​

This release adds some significant new experimental features to Aerie - check out our docs for more details:

  • Aerie now supports Procedural Constraints, Java-based user-defined constraints which may leverage the same libraries used by Procedural Scheduling as an alternative to our declarative/EDSL constraints feature
  • Aerie Actions have been added to our Phoenix sequencing app - these are a powerful new tool allowing users to define custom tasks in Javascript that operate on the sequences in their workspace, to do things like translation, compilation or static checking.
  • Sequence Templates are now supported as a way for users to expand activities in a plan into commands/sequences, as an alternative to our existing Typescript EDSL expansion rules.