> For the complete documentation index, see [llms.txt](https://docs.codeocean.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codeocean.com/user-guide/release-capsules-and-pipelines.md). # Release Capsules and Pipelines A Release Capsule/Pipeline is an end-to-end reproducible and immutable version of your Capsule/Pipeline that is saved in its current state and separate from the original. Releases enable you and your team to use a fully functioning, standardized version while you continue to develop your original Capsule or Pipeline separately. You can release new versions as necessary while maintaining access to previous versions. A Release Capsule or Pipeline that is shared with everyone is known as an "Internal Release" and will show up on the Internal Releases page accessible via the Navigation sidebar. In this guide: 1. [Creating and Using Release Capsules](/user-guide/release-capsules-and-pipelines/creating-and-using-release-capsules.md) 2. [Creating Release Pipelines](/user-guide/release-capsules-and-pipelines/creating-release-pipelines.md) 3. [Internal Releases](/user-guide/release-capsules-and-pipelines/internal-releases.md) ### Release Process Overview {% embed url="" fullWidth="false" %} --- # 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.codeocean.com/user-guide/release-capsules-and-pipelines.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.