<@U12AGS8JG> is the spring extension ready for rel...

# kotest-contributors

[Emil Kantis]

@sam is the spring extension ready for release? Simple as this?

[LeoColman]

Yep

[LeoColman]

We then need to go into Sonatype and close the release

[Emil Kantis]

oss.sonatype.org? how is that done? doesn’t seem to be any github SSO

[LeoColman]

Hm, there isn't. My account has access to the sonatype repository, but only @sam can grant access

[LeoColman]

Let me release it for you

[Emil Kantis]

Ah, okay

[Emil Kantis]

I’ll go ahead with the release build then

[LeoColman]

Ok!

[Emil Kantis]

Release workflow has completed

[Emil Kantis]

Not showing up in https://search.maven.org/artifact/io.kotest.extensions/kotest-extensions-spring yet

[LeoColman]

I confirmed the package in sonatype

[LeoColman]

It says that it takes 15 minutes for you to be able to download it (like via gradle)

[LeoColman]

And up to 6h to find it in maven search

[LeoColman]

It becomes available before it is indexed, if you need it faster hahah

[LeoColman]

But on sonatype's side it's released.

[LeoColman]

Good job @Emil Kantis 😄

[sam]

Thanks guys.

[LeoColman]

@sam I think it's possible to close the Sonatype release without having to login to OSS

[LeoColman]

Did you set that up as a 2FAish measure? Or else we can add that step to the release pipeline

[sam]

If you can do it automatically then great

[Emil Kantis]

Likewise @LeoColman 🙌 Updated my projects to use it 🦜

[sam]

@Emil Kantis to get access to sonatype you have to make an account with them and create a ticket requesting access. They will then ask me to confirm as I own tbe domain name.

[Emil Kantis]

Okay ✌️

[Emil Kantis]

Here https://my.sonatype.com/?

[sam]

https://issues.sonatype.org

[Emil Kantis]

Created ticket, thanks 🙂