It's affecting us everywhere, I don't know if ther...
# configs
j
It's affecting us everywhere, I don't know if there was a solution yet <!subteam^S016E36N7TQ> / <!subteam^S044DU0NG68> (I'm at a conference today so difficult to investigate deeply)
elmofire 3
r
it's is only the latest-edge, right?
j
Yes, sorry by everywhere I mean across all repos
(that call nextflow)
m
that's it
r
ok, looks like the
latest-everything
is doing what it is supposed to do 😄
m
as Matthias was saying, Java11 is being left behind, I believe GHA will update that next year, in the meantime, this is an easy fix
j
💯
m
I think to remember we had some option to have the latest release but not edge
m
we will actually do an easier fix and update setup-nextflow with it
🎉 2
m
I was exactly thinking about this
but it's still in GHA
If I remember well, we did start playing with edge more because of modules
r
that and to catch any incompatibilities with the next stable nextflow release early so we can fix the pipelines beforehand
party this 1
p
I'm working on fixing the
setup-nextflow
action now, that will hopefully be a universal fix for the Java 11 CI failures
🎉 2
a
edge is a good idea - we were a bit blindsided by the Java deprecation. It's on us (Seqera) to communicate these breaking changes better. But this is the testing working. We've caught an error early enough while the damage radius is very small.
💯 3
this 6