Release Principles
Reelevant ships continuously. Integrations are built to keep working across releases without action on your side.Major Releases
A major release is any change that could require action from an integrator — for example a change to an existing API response, a removed parameter, or a change in default behaviour. For these releases:- At least 30 days’ notice before the change reaches production
- Notice is sent to the technical contacts on your account and published on the status page
- The notice states what changes, which endpoints or Workflows are affected, and what action (if any) is required
- Where feasible, the previous behaviour remains available during the notice period so you can migrate on your own schedule
Routine Releases
Routine releases — bug fixes, performance work, new Node types, new Datasource connectors, UI improvements — are deployed without prior notice because they do not change existing behaviour. They are listed on the status page alongside maintenance windows.What to Do on Your Side
- Treat API responses as extensible: ignore fields you do not recognise instead of failing on them
- Keep at least one technical contact on the account subscribed to release notices
- Subscribe to the status page for deployment and incident notifications
Next Steps
Status & Monitoring
Deployment notices, availability, and incident communication.
Security & Compliance
Certifications, vendors, audit logging, and how to report a security issue.