Skip to content

Update to topics telseq#11036

Merged
pinin4fjords merged 6 commits intomasterfrom
telseq-topic-versions
Mar 24, 2026
Merged

Update to topics telseq#11036
pinin4fjords merged 6 commits intomasterfrom
telseq-topic-versions

Conversation

@pinin4fjords
Copy link
Member

@pinin4fjords pinin4fjords commented Mar 24, 2026

Summary

  • Migrate telseq module from legacy versions.yml file emission to topic-based version channels
  • Both telseq and samtools versions now emitted via topic: versions
  • Pin bamtools=2.5.2 in environment.yml to fix conda runtime failure (libbamtools.so.2.5.2 not found when solver picks bamtools 2.5.3)
  • Rebuild containers via Wave from the updated environment
  • Hardcode telseq version as 0.0.2 (the binary --help misreports 0.0.1)

Test plan

  • All 4 existing nf-test cases pass with --update-snapshot (docker)
  • Version commands verified in container: telseq 0.0.2, samtools 1.20
  • Hardcoded version pattern matches established modules (bamcmp, cafe, adapterremovalfixprefix, etc.)

🤖 Generated with Claude Code

Migrate telseq module from legacy versions.yml to topic-based version emission for both telseq and samtools.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@pinin4fjords
Copy link
Member Author

pinin4fjords commented Mar 24, 2026

Conda failures were caused by bamtools 2.5.3 being resolved instead of 2.5.2, breaking the telseq shared library link. Fixed by pinning bamtools=2.5.2 in environment.yml and rebuilding containers via Wave.

pinin4fjords and others added 5 commits March 24, 2026 16:24
telseq links libbamtools.so.2.5.2 but conda solver could pick bamtools
2.5.3 (which provides libbamtools.so.2.5.3), causing runtime failure.
Pin bamtools=2.5.2 in environment.yml and regenerate containers via Wave.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The telseq binary --help output reports Version 0.0.1 even in the
0.0.2 conda package. Hardcode the correct version using the echo
pattern used by other modules with the same issue.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The nf-core linter requires the topics section to list the exact
tool names and version commands from main.nf, not generic placeholders.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@pinin4fjords pinin4fjords added this pull request to the merge queue Mar 24, 2026
Merged via the queue into master with commit e307188 Mar 24, 2026
28 checks passed
@pinin4fjords pinin4fjords deleted the telseq-topic-versions branch March 24, 2026 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants