> 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 A software development practice where code changes are automatically built, tested, and prepared for a release to production. 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.