> For the complete documentation index, see [llms.txt](https://docs.polygonflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes.md).

# 发布说明

- [Dash 1.12.0](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.12.0.md): Dash 1.12 重点修复了我们现有工具中的许多较小但重要的问题。当然，此版本还包含对 UE 5.8 的支持。
- [Dash 1.11.0](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.11.0.md): Dash 1.11 引入了可绘制预设、新预设以及更快、更灵活的内容浏览器。
- [Dash 1.10.0](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.10.0.md): 一次构建，随处使用。
- [Dash 1.9.3](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.9.3.md)
- [Dash 1.9.2](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.9.2.md)
- [Dash 1.9.0](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.9.0.md)
- [Dash 1.8.5（正式版）](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.8.5.md)
- [Dash 1.8.0](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.8.0.md): 我们努力确保 Dash 1.8 比之前的版本进一步提升了世界构建流程，而更重要的是，现在 Dash 更易于使用，也更容易上手！
- [Dash 1.7.0](https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes/dash-1.7.0.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.polygonflow.io/dash-documentation-zh/gao-ji/release-notes.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.