Changelog

A new field, version_comment, has been added to several existing API endpoints.

For the Developer API:

• GET /api/recipes
• GET /api/recipes/:id

For the Embedded API:

• GET /api/managed_users/:id/recipes
• GET /api/managed_users/:id/recipes/:recipe_id

On the Deployments tab of a project, you can now view the entire deployment history as a timeline, complete with status, environment, comments, and the full manifest of the deployment.

Only users with deployment permissions can see this tab. Project deployment logs are only available in the Development environment.

When exporting a manifest via Recipe Lifecycle Management, the error messaging is now more actionable to assist in fixing any missing assets. For help with troubleshooting, review our documentation.

Within Recipe Lifecycle Management, archived manifests will behave the same as deleted recipes in the Trash folder and will be permanently deleted after 30 days. With this change, we expect an improved loading time of the Export and Import manifest pages.

Within Recipe Lifecycle Management, the manifest file name format has been updated from `{folder name}_{user name}` to `{manifest name}_{folder name}`. This change was made to enable users to easily find and identify their manifests, and easily match downloaded manifests and the Export/Import UI.

Within the Logging Service, you can now view trigger errors to assist in troubleshooting. As trigger errors do not generate a job, this visibility into the failed triggers is crucial for resolving errors and maintaining the functionality of your recipes.

A Project filter has been added to the lookup table page, to aid in navigating the list of available tables. To associate a lookup table with a specific project, navigate to the lookup table, and select the project icon under the table name.

You can now export up to 1000 rows of job history from the Jobs tab, to aid in compliance or data analysis efforts. The row count does take into account any filters applied.

To make it easier to work with projects after deployment, the RecipeOps trigger now includes the package_id. With this package_id, you can confirm which recipes were deployed via API.

When viewing your exported and imported manifests within Recipe Lifecycle Management, you can now sort the page based on either latest activity, or A > Z to find manifest packages more quickly.