# Chupacabra

Versioned deployments, faster AI··Task, new LLM models, and LLM tokens exposed. The chupacabra, a legendary creature from Latin American folklore, is said to attack and drink the blood of livestock, particularly goats

## NEW

### Deploy a specific flow version 🔢

Ref: #7222

You can now deploy a specific version of a flow, ensuring that your production deployments remains stable while you continue to make edits.

After [creating a new version](https://docs.mindflow.io/changelog/ewoks#2815cc0f00c24fba86b7c60d700f4e30) of a flow, click on the ··· menu at the top right of the flow card and select `Deploy flow...`

   <div class="docs-screenshot-compact">

![Deploy specific flow version](./assets/deploy-specific-flow-version.png)

   </div>

A popup will appear, asking for the following information:

- The destination environment
- The version to use

   <div class="docs-screenshot-compact">

  ![Version use](./assets/version-use.png)

   </div>

This allows you to have multiple versions of the same flow deployed.

   <div class="docs-screenshot-compact">

![Version use](./assets/version-use-2.png)

   </div>

In the designer, you can still quickly switch between different deployments using the top bar.

   <div class="docs-screenshot-compact">

![Version use](./assets/version-use-3.png)

   </div>

Here are a few things to keep in mind:

- **Automatic updates for `Latest` version**

  If a flow is set to `Latest`_,_ all its deployments will be updated automatically when the flow is modified. This can be very useful depending on the use case, as it allows you to keep multiple deployments in sync.

  For example, if you create a flow and deploy it in two environments using the `Latest` version, any changes made to the flow will affect both deployments.

- **Immutable Versions**

  A specific version (e.g., `V1`) cannot be modified. Therefore, if you have deployments set to a specific version of a flow, they will not be affected by changes made to the flow `Latest` version.

  For example, if you create a flow and deploy it in two environments using version `V1` any subsequent changes to the flow will not affect these deployments.

:::note
The ability to update a deployment version (e.g., from `V1` to `V2`) will be available in the next release.
:::

### New LLM models for AI··Task 🧠

Ref: #8600

We have added several new LLM models to enhance your AI··Task capabilities:

- **Amazon Nova Lite** - Optimized for enterprise tasks with balanced performance and cost efficiency. Great for text summarization and general content generation.
- **Amazon Nova Pro** - Higher capability model with enhanced reasoning and complex task handling. Ideal for technical content creation and advanced analytical responses.
- **Llama 3.2 3B** - Compact but powerful open-source model that excels at instruction following and creative writing while being resource-efficient.
- **Mistral Pixtral Large** - Powerful large language model with advanced text processing capabilities, excellent reasoning abilities, and sophisticated content generation for complex tasks.

   <div class="docs-screenshot-compact">

  ![Mistral pixtral large](./assets/mistral-pixtral-large.png)

   </div>

:::note
We'll soon extend model selection to AI··Rooms as well.
:::

## CHANGES

### Add LLM token usage for AI··Task 📊

Ref: #8604

Thanks to your feedback, we have added metadata to help you understand AI token usage, including input tokens, output tokens, and total tokens, for improved tracking and analysis.

   <div class="docs-screenshot-compact">

![Mistral pixtral large](./assets/mistral-pixtral-large-2.png)

   </div>

### Reduce AI··Task latency ⏱️

Ref: #8538

We have improved AI··Task performance by eliminating redundant streaming events, resulting in reduced latency.

## FIXES

- AI··Task: Fixed an issue where shared memory across executions caused tool configuration errors; memory is now isolated per task. (#8618)
- Fixed a crash when pasting a step inside a For Each block, which prevented the flow from loading properly. (#8563)
- Infinite execution in the synchronous webhook response step. (#8158)

## INTEGRATIONS

- [Adobe Workfront](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/workfront-api)
- [Aircall (version: 1.0.0)](https://aircall.io)
- [Braze (version: 1.0)](https://www.braze.com)
- [Broadcom Cloudhealth (version: v1)](https://www.cloudhealthtech.com/)
- [Dbt Labs Cloud (version: 2.0.0)](https://www.getdbt.com/product/dbt-cloud/)
- [IBM Cloud Pak for Watson AIOps - Issue Resolution (version: 1.0)](https://www.ibm.com/cloud/cloud-pak-for-watson-aiops)
- [IBM Cloud Pak for AIOps - Metric API Service (version: 1.0)](https://www.ibm.com/cloud/cloud-pak-for-aiops)
- [IBM Cloud Pak for AIOps - Runbook Automation (version: 1.0)](https://www.ibm.com/cloud/cloud-pak-for-aiops)
- [IBM Cloud Pak for AIOps - Change Risk (version: 1.0)](https://www.ibm.com/cloud/cloud-pak-for-aiops)
- [Jenkins](https://www.jenkins.io/)
- [QR Code Generator (version: 1.0.0)](https://www.qr-code-generator.com/)
- [ServiceNow Change Management (version: v1)](https://www.servicenow.com/docs/fr-FR/bundle/washingtondc-api-reference/page/integrate/inbound-rest/concept/change-management-api.html)