update docs

nf-core · Nov 13, 2024 · 88b5322 · 88b5322
1 parent 0052ee0
commit 88b5322
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/usage.md b/docs/usage.md
@@ -323,7 +323,7 @@ nextflow pull nf-core/ampliseq
 
 It is a good idea to specify a pipeline version when running the pipeline on your data. This ensures that a specific version of the pipeline code and software are used when you run your pipeline. If you keep using the same tag, you'll be running the same version of the pipeline, even if there have been changes to the code since.
 
-First, go to the [nf-core/ampliseq releases page](https://github.com/nf-core/ampliseq/releases) and find the latest pipeline version - numeric only (eg. `2.4.1`). Then specify this when running the pipeline with `-r` (one hyphen) - eg. `-r 2.4.1`. Of course, you can switch to another version by changing the number after the `-r` flag.
+First, go to the [nf-core/ampliseq releases page](https://github.com/nf-core/ampliseq/releases) and find the latest pipeline version - numeric only (eg. `2.12.0`). Then specify this when running the pipeline with `-r` (one hyphen) - eg. `-r 2.12.0`. Of course, you can switch to another version by changing the number after the `-r` flag.
 
 This version number will be logged in reports when you run the pipeline, so that you'll know what you used when you look back in the future. For example, at the bottom of the MultiQC reports.