> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/basespace/releases/previous-releases/2026/7.42.0.md).

# 7.42.0 - BaseSpace CLI 1.7.0

#### January 20, 2026

#### Features

* Updated the BaseSpace CLI to version 1.7.0. Download the latest version and see the release notes [here](https://developer.basespace.illumina.com/docs/content/documentation/cli/cli-releasenotes).
* Improved error messages returned by sample sheet validation during Requeue Analysis, Library QC App launch, and Import Run.
* Allow Dataset file to be imported as Reference File for Run Planning
* Improve performance of project list.

#### Bugs Fixed

* Fixed native app cost discrepancy between BaseSpace and UPA.
* More reliable indexing of output files from analyses that are automatically transitioned to "timed out" status.
* Set standard input properties on ICA analyses, improving behavior in context of automated workflows.

#### Downloader 3.2

* Properly sanitize filenames containing characters not supported by the user's operating system.
* Multiple UI improvements and bugfixes

#### Known Issues

* The copy and merge features are currently unavailable for samples generated by BCL Convert.


---

# 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://help.bioinsight.illumina.com/basespace/releases/previous-releases/2026/7.42.0.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.