> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/api/client-libraries/redivis-js/reference/dataset/dataset.release.md).

# Dataset.release

### Dataset.<mark style="color:purple;">release</mark>(*\[{ releaseNotes, waitForFinalization, signal }]*) → `Promise<Dataset>`

Releases the dataset's next version, making it the current version.

**Parameters:**

**`releaseNotes`** : *string, optional*\
Notes describing the changes in this version.

**`waitForFinalization`** : *boolean, default false*\
Whether to wait for the release to be finalized before resolving. The release takes effect immediately, but the version's data is finalized in the background, and until that finishes, the dataset's versions can't be released, unreleased, or deleted. Set this to `true` if you'll make another such change right after this one, e.g., when releasing several versions in quick succession.

**`signal`** : *AbortSignal, optional*\
Stops waiting for the release to be finalized. This doesn't cancel the release.

**Returns:** `Promise<Dataset>`, this dataset, at the newly released version.


---

# 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.redivis.com/api/client-libraries/redivis-js/reference/dataset/dataset.release.md?ask=<question>&goal=<user_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.
