# Versioning Question for the nf-core/pacvar Release

**URL:** <https://community.seqera.io/t/versioning-question-for-the-nf-core-pacvar-release/2690>\
**Category:** Ask for help\
**Created:** [May 25, 2026, 7:29pm UTC](https://community.seqera.io/t/versioning-question-for-the-nf-core-pacvar-release/2690 "2026-05-25T19:29:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chaochaowong](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/chaochaowong/32/2232_2.png) [@chaochaowong](https://community.seqera.io/u/chaochaowong)\
**Post date:** [May 25, 2026, 7:29pm UTC](https://community.seqera.io/t/versioning-question-for-the-nf-core-pacvar-release/2690/1 "2026-05-25T19:29:28Z")

</div>

The current release version of `pacvar` is `1.0.1` (first metro below). Since then, we have added six major modules to the pipeline (second metro belowO: `hificnv` (copy number variats), `pbmerge` (to merge fail bam), `sawfish` (structural varians), `pbcpgtools` (5mC methylation), `ensemblvep` (annotation), and `fibertools` (m6A/nucleosome processing). Together, these additions substantially expand the pipeline’s ability to support PacBio long-read sequencing analysis.

This represents a major update from `1.0.1`. At the moment, the development version is still labeled `1.1.0.dev`. Should we keep the next release version as `1.1.0`, or would it be more appropriate to bump it to `2.0.0`?

v.1.0.1

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/8/8a6adf36702183441a93b211e1f0548c90dec0f3.jpeg)  
v1.1.0dev  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/0/0793178f3663a74e37a34eaf76fdd9722d9f26ef.jpeg)

Thank you,  
Chao-Jen Wong

---

<div class="post-metadata">

**Author:** ![GeraldineVdA](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/geraldinevda/32/178_2.png) [@GeraldineVdA](https://community.seqera.io/u/GeraldineVdA)\
**Post date:** [June 4, 2026, 9:00am UTC](https://community.seqera.io/t/versioning-question-for-the-nf-core-pacvar-release/2690/2 "2026-06-04T09:00:48Z")

</div>

Hi @chaochaowong , I think this is more a question to ask in the nf-core Slack since it’s so specific to nf-core.

---

<div class="post-metadata">

**Author:** ![mribeirodantas](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/mribeirodantas/32/235_2.png) [@mribeirodantas](https://community.seqera.io/u/mribeirodantas)\
**Post date:** [June 4, 2026, 10:06am UTC](https://community.seqera.io/t/versioning-question-for-the-nf-core-pacvar-release/2690/3 "2026-06-04T10:06:34Z")

</div>

Hi @chaochaowong,

Versioning of nf-core pipelines follows Semantic Versioning. You can check it at the nf-core page clicking [here](https://nf-co.re/docs/specifications/pipelines/requirements/semantic_versioning). Based solely on what you shared, I don’t see breaking changes, so I’d say it’s a minor release and I’d recommend going from 1.0.1 to 1.1.0.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)\
**Post date:** [June 11, 2026, 10:06am UTC](https://community.seqera.io/t/versioning-question-for-the-nf-core-pacvar-release/2690/4 "2026-06-11T10:06:55Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.