I was wondering if anyone has the same observation...
# team-maintainers
j
I was wondering if anyone has the same observation: I find myself running more and more into nextflow errors with latest versions, actually anything beyond 25.10.04 tends to be flaky. What about introducing an upper bound nextflow version (that the devs can define)? This would reduce user friction and frustrations here and there, since these errors can be quite cryptic / hard to debug
m
I have the same impression.. I feel like there’s a push for new features, but the testing is lacking
Or they’re using the nf-core community as a test bed...
j
👍 Let’s talk about it in maintainers meeting
p
It's already possible to specify upper bound versions, has been for years
But please please please report any cryptic messages! 🙏🏻😅
It's the only way we can fix them. We put stuff out as previews for people to try out but in reality very few do, so we rely on early adopters finding any edge cases that we miss during development.
🫡 1
j
Sure, will do 🙂 great, thanks for bringing this up that its already possible
👍🏻 1