Update libs

[altro3]

Fixed checkstyle errors.

[altro3]

@graemerocher @sdelamo Important PR: need to update dependencies, becuase some vulnurabilities found:

[sdelamo]

build fails

[altro3]

@sdelamo that's not my fault

I checked locally - everything works fine

[altro3]

@sdelamo could you fix this problem? Other PRs failed because of this too:

#1390
#1370
#1369
#1368

[lissam1]

@sdelamo could you fix this problem? Other PRs failed because of this too:

#1390 #1370 #1369 #1368

try to merge i merged a pr which was failing with same failure you have

[altro3]

@lissam1 I haven't rights to merge in this repo. I can only in micronaut-openapi

[lissam1]

@lissam1 I haven't rights to merge in this repo. I can only in micronaut-openapi

i mean merge 4.10.x with your branch

[altro3]

but what about other PRs?

[graemerocher]

they will need to do the same

[altro3]

@lissam1 @graemerocher same result :-(

[lissam1]

@lissam1 @graemerocher same result :-(

it's not same failure you have this initialization issue with native org.junit.jupiter.engine.discovery.MethodSegmentResolver, i think it's related with junit update.

[altro3]

@lissam1 no, result the same. Problem with sonatype scan plugin

look to pipeline logs

[lissam1]

@altro3 i assume because of access, did you run build locally without sonatype task ?

[altro3]

lol, this is just console, just text. I have access to build log and I see this eeror now, but that is not problem with my account.

Did you see it? https://github.com/micronaut-projects/micronaut-test/actions/runs/22712487061/job/65853730375?pr=1389

Of course I ran it locally - all works fine.

Your assumption is completely baseless. Look at other PRs from OTHER contributors (#1369, #1370) - you'll see exactly the same error. What does the junit update have to do with this?

[lissam1]

lol, this is just console, just text. I have access to build log and I see this eeror now, but that is not problem with my account.

Did you see it? https://github.com/micronaut-projects/micronaut-test/actions/runs/22712487061/job/65853730375?pr=1389

Of course I ran it locally - all works fine.

Your assumption is completely baseless. Look at other PRs from OTHER contributors (#1369, #1370) - you'll see exactly the same error. What does the junit update have to do with this?

for native test it's diffrent failures in each PR.
for build what i mean about sonatype maybe cause of some specific access because i create a pr and sonatype pass see #1401

[altro3]

hmmm... Ok, But how we can fix it? Why that works fine on other projects?