We’ve improved how we roll out updates for Appfarm Create! Previously, all Solutions were upgraded simultaneously. Now, we have the flexibility to manage upgrades on a per-solution basis. To structure this process, we’ve defined a set of release channels. The channel your solution is on will control which version of Appfarm Create it uses.
How does it work?
All release channels receive updates at the same pace, with the only difference being the delay from the initial release. The current release cadence is weekly. All release channels will be updated one major version on the night before Thursday. If necessary, high-priority patches for critical bugs or security updates will be applied to all channels immediately.
We currently provide three release channels: Early, Standard and Stable. The default channel for production solutions is Standard, while sandboxes and free trial solutions will be set to Early by default. The release schedule is outlined in the table below.
| Channel | Delay | Note |
|---|---|---|
| Early | The latest public release | Get new features and improvements first! Solutions on the Early channel operate under a relaxed SLA (see below), acknowledging the focus on early access. |
| Standard | One major version behind Early | Recommended channel for most production solutions, offering a balance of new features and proven stability. Standard SLA applies. |
| Stable | One major version behind Standard | Solutions with stringent stability requirements where the latest features are not critical. |
How do I see which release channel my solution is on?
Open the menu in the top-left corner of Appfarm Create, then click About Appfarm Create. This will open a dialog which includes the current version and the release channel your Solution is running.
How do I move my Solution to a different release channel?
Get in touch with your Appfarm representative to discuss moving your Solution to a different release channel.
Why does the Early channel have a “relaxed SLA”?
The Early channel receives the version immediately following rigorous internal validation. Since it is the first channel to expose a given version to a wide external audience, there is an inherently higher risk of encountering non-critical, edge-case bugs. The relaxed SLA reflects this stabilization phase.
Read more about release channels in our Docs.