> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/c/continuous-delivery.md). # Continuous Delivery Continuous Delivery is a software development practice where code changes are automatically built, tested, and prepared for release to production. The key distinction from Continuous Deployment is that Continuous Delivery requires a manual approval step before changes are deployed to production, giving teams control over release timing. A Continuous Delivery pipeline typically includes automated unit tests, integration tests, security scans, and staging deployments. The goal is to ensure that the codebase is always in a deployable state, reducing the risk and effort associated with releases. This enables teams to ship smaller, more frequent updates. For API and serverless projects, Continuous Delivery pipelines automate the deployment of gateway configurations, serverless functions, and API specifications. Changes to routing rules, rate limits, or authentication policies can be tested in staging environments before being promoted to production. This reduces the risk of misconfigurations that could cause outages or security vulnerabilities. --- # 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.serverlessapigateway.com/glossary/c/continuous-delivery.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.