> For the complete documentation index, see [llms.txt](https://techwritingtools.gitbook.io/dockit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://techwritingtools.gitbook.io/dockit/changelog/readme.md).

# Changelog

New updates and improvements

{% updates format="full" %}
{% update date="2026-08-15" tags="feature,improvement,fix" %}

## What's new in version 0.3.2

**Updated documentation:** Updated the README and CHANGELOG for improved clarity and readability. No extension functionality was changed.
{% endupdate %}

{% update date="2026-08-14" tags="feature,improvement,fix" %}

## What's new in version 0.3.1

Version 0.3.1 adds several new capabilities and updates:

<div align="left"><figure><img src="https://1071336608-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPQ46mDCdGCv4FsbFOfOk%2Fuploads%2FtfXXJxbiUCAw3PiEawX0%2Ffull-ui.png?alt=media&amp;token=a7d33061-f98b-47cc-9659-9c3d511d0426" alt=""><figcaption></figcaption></figure></div>

* API linting is now configurable and opt-in.
* 19 DocKit governance rules were added.
* The **Open Rules Reference** catalog provides a browsable list of linting rules and styles.
* Optional Vale-based prose style checks were added for Google, Microsoft, IBM, write-good, and alex styles.
* Custom inline and external spell-check dictionaries are supported.
* **Export Public Spec** removes internal operations without modifying the source specification.
* Optional conservative component pruning was added to public export.
* The OpenAPI Outline view can group endpoints by tags.
* Spelling and Style findings are now separate groups in **All Issues**.
* Style suggestions appear in the Problems panel and can provide quick fixes.

### Fixes

* The bundled dictionary was rebuilt to reduce false positives from obscure words.
* JSON editor schema validation is version-aware for Swagger 2.0, OpenAPI 3.0.x, and OpenAPI 3.1.x.
  {% endupdate %}

{% update date="2026-06-13" tags="feature,fix" %}

## Initial release

See what’s new and improved in our latest update.

<div align="left"><figure><img src="https://gitbookio.github.io/onboarding-template-images/placeholder.png" alt=""><figcaption></figcaption></figure></div>

<a href="/dockit/changelog/2026/product-update-1.md" class="button primary">Read full update</a><a href="https://gitbook.com/" class="button secondary">Documentation</a>

<details>

<summary>Fixed</summary>

* Product fix
* Product fix
* Product fix
* Product fix
* Product fix

</details>
{% endupdate %}
{% endupdates %}


---

# 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://techwritingtools.gitbook.io/dockit/changelog/readme.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.