> For the complete documentation index, see [llms.txt](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfactor.io/52eJroWboQfTwsFl14gL/docs-release-notes/release-approach/release-approach.md). # Release Approach Releases are continuous, controlled, and backward compatible by default. The objective is to deliver incremental value with minimal disruption and full transparency. ### Continuous Delivery Model We operate a rolling release model: enhancements, fixes, and performance improvements are deployed regularly rather than bundled into infrequent major upgrades. This enables faster innovation and shorter feedback loops. ### Safe and Controlled Rollouts Releases follow a staged promotion path: * Internal validation * Automated regression and security testing * Gradual production rollout This approach minimizes risk and ensures stability across environments. ### Backward Compatibility API contracts and integrations are maintained wherever possible. When breaking changes are unavoidable: * They are clearly documented in advance * Deprecation periods are provided * Migration guidance is published ### No Customer-Managed Upgrades Updates are applied automatically. Customers always run the latest secure and supported version without manual intervention. ### Feature Controls New capabilities may be introduced behind feature flags to: * Enable controlled activation * Support phased adoption ### Release Notes Transparency Every production release is documented and categorized: * New features * Improvements * Fixes * Security updates Where relevant, impact and configuration changes are explicitly stated. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.appfactor.io/52eJroWboQfTwsFl14gL/docs-release-notes/release-approach/release-approach.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.