> For the complete documentation index, see [llms.txt](https://docs.datasaur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasaur.ai/compatibility-and-updates/release-notes/version-6/6.25.0.md). # 6.25.0 August 16, 2023 ## **What's new** 💡 * The Extension panel will now automatically collapse after disabling all extensions. * We add the latest time information when the IAA data is updated. This information perfectly matches the time when the last labeler marked the document as complete. * We have enhanced the tooltip for a long project name. * We simplify your labeling process through automation, Datasaur Predictive Labeling, by providing us with a mere five data samples. ## **Bug fixes** 🐞 * Fixed an issue that allowed users to upload answer set with duplicate answer label for Dropdown, Hierarchical dropdown, and Radio question types. * Fixed an issue that displayed incorrect questions when saving the question set to the library. * Fixed an issue where holding Shift after applying labels would result in selecting more text than intended. * Fixed an issue where page navigation doesn’t work properly when the row filter is activated. * Fixed an issue where the context menu wouldn’t appear upon clicking “Edit” in the table viewer header. * Fixed an issue where users were able to switch between labeler and reviewer modes even after changing the project status to "Mark Project as Complete”. * Fixed an issue where users were unable to switch to labeler mode after changing the project status from "Mark Project as Complete" to "In Review”. --- # 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.datasaur.ai/compatibility-and-updates/release-notes/version-6/6.25.0.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.