|
1 | 1 | (migrating-26-04-page)= |
2 | 2 |
|
3 | | -# Migrating to 26.04 (preview) |
| 3 | +# Migrating to 26.04 |
4 | 4 |
|
5 | | -This page summarizes the upcoming changes in Nextflow 26.04, which will be released in April 2026. |
6 | | - |
7 | | -:::{note} |
8 | | -This page is a work in progress and will be updated as features are finalized. It should not be considered complete until the 26.04 release. |
9 | | -::: |
| 5 | +[Nextflow 26.04](https://github.com/nextflow-io/nextflow/releases/tag/v26.04.0) was released on April 29, 2026. |
10 | 6 |
|
11 | 7 | ## New features |
12 | 8 |
|
@@ -164,20 +160,38 @@ Breaking changes from the {ref}`first preview <static-typing-first-preview>`: |
164 | 160 |
|
165 | 161 | - The syntax for process tuple inputs has been updated: |
166 | 162 |
|
167 | | - ```nextflow |
168 | | - // 25.10 |
169 | | - input: |
170 | | - (id, fastq_1, fastq_2): Tuple<String,Path,Path> |
| 163 | + ```nextflow |
| 164 | + // 25.10 |
| 165 | + input: |
| 166 | + (id, fastq_1, fastq_2): Tuple<String,Path,Path> |
171 | 167 |
|
172 | | - // 26.04 |
173 | | - input: |
174 | | - tuple(id: String, fastq_1: Path, fastq_2: Path) |
175 | | - ``` |
| 168 | + // 26.04 |
| 169 | + input: |
| 170 | + tuple(id: String, fastq_1: Path, fastq_2: Path) |
| 171 | + ``` |
176 | 172 |
|
177 | 173 | - The method signature for the `stageAs` directive was changed from `(filePattern, value)` to `(value, filePattern)`. |
178 | 174 |
|
179 | 175 | See {ref}`migrating-static-types` for more information about migrating to static typing. See {ref}`migrating-static-types-operators` for best practices on using operators with static typing. |
180 | 176 |
|
| 177 | +<h3>Process <code>hints</code> directive</h3> |
| 178 | +
|
| 179 | +The `hints` process directive allows you to specify executor-specific hints for individual processes. |
| 180 | +
|
| 181 | +For example, the AWS Batch executor uses the `consumableReources` hint for [resource-aware scheduling](https://aws.amazon.com/about-aws/whats-new/2025/02/aws-batch-resource-aware-scheduling/): |
| 182 | +
|
| 183 | +```nextflow |
| 184 | +process hello { |
| 185 | + hints 'awsbatch/consumableResources': ['my-license': 1] |
| 186 | +
|
| 187 | + // ... |
| 188 | +} |
| 189 | +``` |
| 190 | + |
| 191 | +Custom executors can use hints to control scheduling behavior in a fine-grained manner over configuration options. |
| 192 | + |
| 193 | +See {ref}`process-hints` for details. |
| 194 | + |
181 | 195 | ## Enhancements |
182 | 196 |
|
183 | 197 | <h3>Strict syntax parser enabled by default</h3> |
@@ -218,10 +232,6 @@ Nextflow uses the default branch specified by the Git repository when no revisio |
218 | 232 |
|
219 | 233 | The `manifest.defaultBranch` config option is no longer needed because of this update. |
220 | 234 |
|
221 | | -<h3>Load collection-type params automatically from files</h3> |
222 | | - |
223 | | -When using the `params` block, collection-type parameters such as `List<Record>` can be loaded automatically from a CSV, JSON, or YAML file. This feature simplifies the loading of samplesheet inputs and allows a pipeline to support multiple structured data formats. |
224 | | - |
225 | 235 | See {ref}`workflow-typed-params` for details. See {ref}`migrating-static-types` for a migration example. |
226 | 236 |
|
227 | 237 | <h3>Print workflow outputs on run completion</h3> |
@@ -339,6 +349,33 @@ workflow RNASEQ { |
339 | 349 |
|
340 | 350 | See the {ref}`cli-lint` command reference for details. |
341 | 351 |
|
| 352 | +<h3>Apple container support</h3> |
| 353 | + |
| 354 | +Nextflow can run containers on macOS using [Apple container](https://github.com/apple/container), a lightweight container runtime for Apple silicon machines: |
| 355 | + |
| 356 | +```groovy |
| 357 | +process.container = 'nextflow/examples:latest' |
| 358 | +appleContainer.enabled = true |
| 359 | +``` |
| 360 | + |
| 361 | +See {ref}`container-apple` for details. |
| 362 | + |
| 363 | +<h3>Seqera filesystem for datasets</h3> |
| 364 | + |
| 365 | +Nextflow can download [Seqera Platform datasets](https://docs.seqera.io/platform-cloud/data/datasets) using the `seqera` URI scheme. |
| 366 | + |
| 367 | +Seqera dataset URIs are specified as `seqera://<organization>/<workspace>/datasets/<name>[@version]`. For example: |
| 368 | + |
| 369 | +```nextflow |
| 370 | +params.dataset = 'seqera://seqeralabs/showcase/datasets/sarek_samples' |
| 371 | +
|
| 372 | +workflow { |
| 373 | + println file(params.dataset).text |
| 374 | +} |
| 375 | +``` |
| 376 | + |
| 377 | +A Platform access token with appropriate permissions is required to download non-public datasets. It can be specified using the `TOWER_ACCESS_TOKEN` environment variable or the `tower.accessToken` config option. |
| 378 | + |
342 | 379 | ## Breaking changes |
343 | 380 |
|
344 | 381 | - The {ref}`strict syntax parser <strict-syntax-page>` is now enabled by default. The legacy parser can be enabled by setting the `NXF_SYNTAX_PARSER` environment variable to `v1`. |
|
0 commit comments