> For the complete documentation index, see [llms.txt](https://docs.desci.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.desci.com/create-and-publish/publish/update-your-node/publish-a-new-version-of-your-research-node.md).

# Publish a new version of your Research Node

## Versionability

Part of the versatility of DeSci Nodes is the ability to update publications, and yet have a continuous track record of versions. For any publications, previous versions are shown and accessible. These versions can be found in the top navigation bar, after 'Home'. The version number will be visible as 'vX', and this is clickable - rolling out a menu of previous versions. Here you can choose the version you would like to explore. As you publish a new version of your work, this number will increase and earlier versions will be available in the version menu.

## Publish the new version

Publishing a new version of your Node works exactly like [publishing for the first time](/create-and-publish/publish.md). 


---

# 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.desci.com/create-and-publish/publish/update-your-node/publish-a-new-version-of-your-research-node.md?ask=<question>&goal=<endgoal>
```

`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.