Bump Nextflow training environment to 26.04.4#969
Merged
Conversation
✅ Deploy Preview for nextflow-training ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…bleshooting note [skip ci]
… 26.04 output [skip ci]
… 4 snippets [skip ci]
The positional form 'cowpy "Hello Containers"' does not put the text in the speech bubble (cowpy reads the message from stdin); it printed the cowacter self-description. Use the stdin form, matching how the pipeline module invokes cowpy, so the documented output is what the command actually produces. [skip ci]
… under v1 parser) [skip ci]
… default [skip ci]
… nf-co2footprint 1.2.0->1.3.0 [skip ci]
…utput for 26.04 (v1) [skip ci]
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
… hash consistency [skip ci]
…rror text + output) [skip ci]
…st-merge with #961 publishing [skip ci]
…prose for v2 static type checking [skip ci]
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Nextflow linting complete!
💡 Tip: Click filename locations to go directly to that code. View all 70 issuesView formatting changes
|
…a typed params.yaml Validated end-to-end on native x86 (22-task molkart run). Resolves the v2 integer-param typing issue (--flag value ints arrive as strings under the v2 parser) by switching documented commands to a typed params.yaml; also fixes a fabricated resume block and a wrong task count. [skip ci]
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
mribeirodantas
approved these changes
Jun 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the training environment to Nextflow 26.04.4 (from 25.10.4) and refreshes the materials to match.
This is not a find-and-replace. Nextflow 26.04 makes the v2 syntax parser the default, and console output, file listings, and some behaviours change versus 25.10. Every runnable tutorial was re-run end-to-end on 26.04.4 (in Docker,
NXF_VER=26.04.4) and its documented output regenerated from genuine runs. No fabricated or hand-edited output.What changed
NXF_VER→26.04.4in both devcontainer configs.info/nxf_versions.mdrewritten: the "v2 parser will become the default in 26.04" statements are now present-tense, and the loaded-version note is 26.04.4. The supported floor stays 25.10.2 (still valid with the v2 parser enabled).Outputs:summaries, error text, and file listings refreshed from real 26.04.4 runs across the modules below.Verified on 26.04.4 (default v2 parser)
hello_nextflow(Parts 1-6)nextflow_run+envsetupnf4_science— genomics + rnaseq (VCFs byte-matched) and imaging/molkart (full 22-task run on native x86)side_quests— all 9 (debugging, dev_environment, essential_scripting_patterns, metadata, nf_test, plugin_development, splitting_and_grouping, workflows_of_workflows, working_with_files), each verified by a dedicated runConfirmed across every module: 26.04 required no script changes — the v2-syntax scripts already parse and run cleanly. All real changes are console-output formatting: the version banner, the
Launchingline droppingDSL2, the process status line ([hash] NAME | N of M ✔), and the new end-of-runOutputs:summary block.Incidental fixes (found along the way)
hello_nextflow/04: stalegreetingparam corrected toinput(mismatched the solution; would nullparams.input).hello_nextflow/05+nextflow_run/02: cowpy demos used the positional form (cowpy "Hello Containers"), which doesn't put the text in the speech bubble (cowpy reads stdin). Switched to the stdin form so the documented output matches, consistent with how the pipeline module invokes cowpy.nf4_science/rnaseq/03: MultiQC data-dir listing refreshed to current tool output.nf4_science/imaging: was lagging at 25.04.3; brought up to 26.04 and made v2-safe by switching molkart's documented integer params from CLI flags (which arrive as strings under the v2 parser and fail validation) to a typedparams.yaml. Also fixed a fabricated resume block and a wrong task count.Deliberately scoped out (one follow-up)
hello_nf-corestays on the v1 parser in this PR (orientation instructsexport NXF_SYNTAX_PARSER=v1). The course is verified working end-to-end on 26.04.4 under v1 (Part 1'snextflow pullexploration steps were updated for 26.04's new on-disk layout, and the fullnf-core/demorun completes). Running it under the v2 default needs a content change (the nf-core--validate_params falseCLI pattern is a no-op under v2 — Using strict syntax causes template to raise an error when setting boolean options on CLI nf-core/tools#4100, still open) and a migration to the nf-core tools 4.0 template. That modernization is a stacked follow-up PR (hello-nf-core-tools-4.0, solutions already migrated and verified).Translations
docs/<lang>/are out of scope here; they are regenerated by the separate translation pipeline.🤖 Generated with Claude Code