> 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.127.0.md). # 6.127.0 August 28, 2025 ## **What's new** 💡 ### **Data Studio** * [Span + Line + Document Labeling](/data-studio-projects/lets-get-labeling/span-based/span-+-line-+-document-labeling.md) — Introducing a new labeling type that combines span, line, and document labeling in a single project. * Multiple Line and Row Selection — Available in Row and Span + Line Labeling projects, users can now select multiple lines or rows at once using checkboxes in the Reviewer Mode, making it easier to review and edit in bulk. ## **Bug fixes 🐞** ### **Data Studio** * Fixed an issue in the Search extension for Span Labeling projects where the number of lines shown in the search results did not match the summary count. * Fixed an issue in the Search extension for Span Labeling projects where the advanced search results displayed line numbers for multi-line labels incorrectly. * Fixed an issue where modifying question sets inside a project caused an “Invalid question index” error when deleting and re-adding a question. * Fixed an issue where modifying question sets inside a project caused newly added questions to incorrectly inherit the “Allow multiple” setting from deleted ones. --- # 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.127.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.