Hello, how to update a container in a module where you actually need the version with the higher build number? (e.g.

0.5.1-r44hdfd78af_1

instead of

0.5.1-r44hdfd78af_0

. Seqera containers happily recycles the build results as the major version didn't change. (Rationale: _1 carries patches essential for the module to work)

Apparently I do not have access to that...

basically just specify the required build on the cli

Oh, I see, I need to check how to do make the singularity links because I had some trouble using the wave CLI (I might need to update it, it's been quite a while), time to dig things up...

Mostly because the docs mention that

freeze

about "private registry" rather than public ones, but I'll first try it

also see https://github.com/nf-core/modules/blob/master/.github/scripts/wave_singularity.py

If you use

--freeze

without

--buildrepo

it'll go to the public registry

Thanks, I picked the public URL for the singularity repo as @Matthias De Smet pointed out, it worked