# Release Schedule

### Feature Wave Release Schedule

<table data-header-hidden><thead><tr><th width="133.83331298828125"></th><th width="175"></th><th width="169"></th><th width="154" align="center"></th><th width="157.16668701171875"></th></tr></thead><tbody><tr><td><strong>Feature Wave</strong></td><td><strong>UAT Deployment</strong></td><td><strong>Production Deployment</strong></td><td align="center"><strong>Supported API Versions</strong></td><td><strong>Custom Card Angular Framework Version*</strong></td></tr><tr><td><strong>April 2026</strong></td><td>Wed April 08, 2026, 12:30 PM UK</td><td>Sat May 09, 2026</td><td align="center">Legacy, V1, V2</td><td>Version 21</td></tr><tr><td><strong>July 2026</strong></td><td>Wed July 08, 2026, 12:30 PM UK</td><td>Sat Aug 08, 2026</td><td align="center">Legacy, V1, V2, V3</td><td>Version 21</td></tr><tr><td><strong>October 2026</strong></td><td>Wed Oct 07, 2026, 12:30 PM UK</td><td>Sat Nov 07, 2026</td><td align="center">V2, V3, V4</td><td>Version 22</td></tr><tr><td><strong>January 2027</strong></td><td>Wed Jan 06, 2027, 12:30 PM UK</td><td>Sat Feb 06, 2027</td><td align="center">V3, V4, V5</td><td>Version 22</td></tr></tbody></table>

***

### How Feature Wave Deployments work

* As soon as a new feature wave is released, all **non-production** and **UAT** environments are upgraded (within a few days).
* There is then a 4 week window available for customers to carry out UAT activities on these non-production environments. Customers can ask for their production environments to be updated to the new feature wave within this period.
* After 4 weeks, ALL production environments will be updated to the new feature wave, specifically on the 5th weekend after the feature wave release date.
* We are expecting testing errors to be minimal as most new features can turned off, so end users will not be impacted after upgrade.

<figure><img src="/files/2HRxlSQVS8plfjmzylcE" alt=""><figcaption></figcaption></figure>

***

#### APIs and Feature Waves

Each Enate Feature Wave introduces new capabilities and may introduce new API versions. Importantly, **adopting a new Feature Wave does not automatically require immediate API changes**. Supported API versions remain available across multiple Feature Waves to give customers control over when to migrate them.

You should review the API Change documentation available in the Release Notes section for each new Feature Wave as it becomes available, to check for new API version changes which impact your integrations, which would therefore require eventual migration.

Deprecated APIs will be highlighted - these remain operational for that Feature Wave, but support for them will be removed when the next Feature Wave arrives or soon after that, and you should plan to replace these by then. APIs which are now beyond their *final supported Feature Wave* will also be shown, confirming that any integrations which reference them will no longer function correctly.

For more detailed information on this topic, please look at the [**Working with APIs and Feature Waves**](/whats-new/feature-waves-an-overview.md#working-with-apis-and-feature-waves) section.

***

#### Angular updates - for Custom Cards

If you are using an advanced Enate Customer Card, please review the Angular versions your code relies on. Your code is built on this framework, and compatibility issues may occur between different Angular releases. When Enate upgrades to a new **major** version of Angular (see above table for Angular version for Feature Waves), you should validate your code against the updated framework to ensure everything continues to work correctly.

We will make every effort to notify you in advance if we are aware of any breaking changes. However, **code ownership and maintenance remain the responsibility of Enate customers. More info here -** <https://angular.dev/reference/releases>

***

### Enate Integration Services Release Schedule

If you are an **Enate Integration Services** customer, please note that this product follows a separate release calendar, as shown in the table below:

| **Release**  | **Enate Integration Services Upgrade Date** |
| ------------ | ------------------------------------------- |
| **February** | **Mar 21, 2026, 11 PM UK**                  |
| **May**      | **Jun 13, 2026, 11 PM UK**                  |
| **August**   | **Sep 12, 2026, 11 PM UK**                  |
| **November** | **Jan 10, 2027 , 11 PM UK**                 |

**No downtime is required for this upgrade. For more details on this, see the link** [**here**](https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/4306141244/SnapLogic+Releases#2026-Calendar)**.**

***

### The Future Roadmap

Our feature roadmap is available at [**feedback.enate.net**](https://feedback.enate.net/), with items as follows::

* **Working On It** – These features are actively being prepared for upcoming releases.
* **Up Next** – These features will follow 'Working on it' items. We’ll share more on these soon.
* **In The Pipeline** – These features form part of our longer-term vision and are currently being researched.
* **Open** – An open forum for ideas and requests. They are not scheduled but are for further discussion.

We use this approach to give customers visibility of our plans and an indication of timelines. We hope you’ll find it useful.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.enate.net/whats-new/release-schedule.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.