Guide to releases

Coassemble ships regular releases. This article explains how releases roll out across servers, what notifications you’ll receive, and what to do to keep partner integrations running smoothly.

Release rollout: the two-stage cadence

Releases happen in two stages:

1. Standard Release server (previously “Production”)
   • Updates land here first, on release day.
   • This is the shared environment that all customers receive updates on by default.
2. Controlled Release server (previously “Enterprise”)
   • Updates land here two weeks later.
   • This shared environment receives the same release after additional validation, giving customers extra preparation time.

Because of this cadence, there’s always a window where the same release is live on one server but not yet on the other.

What you’ll receive from Coassemble

For every release that affects partner integrations, you’ll receive:

• Preview email (2–4 weeks before release)
  • What’s coming
  • Opt-in status
  • Any UI changes
• Reminder email (1–2 days before Standard Release)
• Standard Release confirmation (release day)
  • Includes documentation links
• Controlled Release confirmation (~2 weeks later)
  • Sent when the Controlled Release server receives the same release

For releases with no partner impact, you’ll receive a short FYI so you’re not surprised by any changes.

What to do on release day

If your integration uses the Standard Release server (previously “Production”)

• Watch for the Standard Release confirmation email.
• Run your usual smoke tests for the integration.
• If anything looks off, email vip@coassemble.com.

If your integration uses the Controlled Release server (previously “Enterprise”)

• No action is required on the day the Standard Release ships.
• Use the two-week window to prepare for the same release landing on your server.
• Watch for the Controlled Release confirmation email when it’s your server’s release date.

If you have integrations on both servers

This is a common setup (for example, one environment for dev/test and the other for production).

• Use the two-week gap to validate the release on your Standard Release environment before it lands on your Controlled Release environment.

What to watch for after any release

After each release, it’s worth checking the following:

• Visual changes
  • Review the embedded experience for UI changes that could affect customer workflows.
• Opt-in features
  • Some features ship disabled by default.
  • Confirm whether anything needs to be enabled for your integration.

When something breaks

If a release causes issues for your integration:

• Urgent issues: email vip@coassemble.com with “urgent” in the subject.
• Non-urgent issues: email vip@coassemble.com with a normal subject.

We’ll triage quickly and either resolve or provide a workaround. If you’re on the Standard Release server and a release causes a problem, we may be able to roll back or hotfix as needed.