> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/projects/project-versions/project-version-history.md).
# Viewing the project version history
On the [project overview](/fabricate/projects/viewing-the-project-overview.md), the **Version History** lists every version of the project.
Version History section of the project overview, with the list of project versions
## Information in the project version history
The versions are displayed by creation date, with the most recent version at the top of the list.
For each published version, the list includes:
* The version identifier.
* The version notes.
* When the version was created (for draft versions) or published (for published or prior versions).
* The user who created or published the version.
## Navigating to a version
From the **Version History**, to switch to a specific version, click the version row.
## Updating the version notes
From the **Version History**, to update the version notes:
1. Hover over the row.
2. For a version that has no notes, click **Add notes**.
3. For a version that has notes, click the edit icon.
4. On the notes panel, provide the updated notes.
5. Click **Save**.
---
# 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.tonic.ai/fabricate/projects/project-versions/project-version-history.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.
