> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.22.0/user-guide/private-registry/publishing-private-modules.md).
# Publishing Private Modules
{% hint style="info" %}
**Manage Modules** permission is required to perform this action, please check [Team Management](/2.22.0/user-guide/organizations/team-management.md) for more info.
{% endhint %}
Click **Registry** in the main menu and then click the **Publish module** button
Select an existing version control provider or click **Connect to a different VCS** to configure a new one. See [VCS Providers](/2.22.0/user-guide/vcs-providers.md) for more details.
Provide the git repository URL and click the **Continue** button.
In the next screen, configure the required fields and click the **Publish Module** button.
The module will be published inside the specified organization. On the details page, you can view available versions, read documentation, and copy a usage example.
### Releasing New Versions of a Module
To release a new version of a module, create a new release tag to its VCS repository. The registry automatically imports the new version.
### Deleting Modules
In the Module details page click the **Delete Module** button and then click the **Yes** button to confirm
---
# 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.terrakube.io/2.22.0/user-guide/private-registry/publishing-private-modules.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.
