Changes & Deprecation Policy
RVO is designed to be stable, predictable, and safe to operate in production.
This page explains how platform changes are communicated, how backwards compatibility is handled, and where to find official release information.
How changes are communicated
Section titled “How changes are communicated”All platform changes are announced publicly and proactively.
RVO communicates changes through:
- Blog posts and release announcements
- Dashboard notifications when relevant
- Documentation updates when behavior changes
There are no silent behavior changes.
Changelog and release notes
Section titled “Changelog and release notes”Detailed release notes and platform updates are published on the RVO blog:
The blog serves as the authoritative source for:
- Feature releases
- Infrastructure upgrades
- Behavioral changes
- Deprecation announcements
Documentation always reflects the current, supported behavior, not historical states.
Backwards compatibility
Section titled “Backwards compatibility”RVO aims to maintain backwards compatibility wherever possible.
When a change may affect existing integrations:
- The change is announced in advance
- Migration guidance is provided when applicable
- Deprecation periods are respected
Breaking changes are avoided unless required for security or platform stability.
Deprecations
Section titled “Deprecations”When functionality is deprecated:
- The deprecation is clearly announced on the blog
- A transition path is documented
- A reasonable sunset period is applied
Deprecated behavior continues to function until the announced removal date.
Why this approach
Section titled “Why this approach”Separating documentation, policy, and release communication ensures that:
- Documentation remains accurate and stable
- Release information is timely and discoverable
- Production systems are not surprised by silent changes
This structure reflects how mature infrastructure platforms operate.
What’s next
Section titled “What’s next”For the latest platform updates, feature announcements, and infrastructure changes, visit:
For operational questions or upcoming changes that may affect your integration, monitor dashboard notifications or contact support.