New release

[hacetin]

When do you plan to release a new version?

• We need to upgrade io.grpc-api version, this package depends on version 1.57 and it causes "Panic" errors.
• Also, it has been 7 months since the last release.

[credmond-git]

It seems like the primary maintainer @jamesward no longer works at google as of April. @jamesward do you have any information on who has taken over this repo?

[lowasser]

In James' absence, it's almost certainly just me. I'll try to accomplish this sometime this week.

[jamesward]

Let me know if you need any help! Details are at: https://github.com/grpc/grpc-kotlin/blob/master/BUILDING.md#releasing

[lowasser]

@jamesward it looks like #480 made step 2 of those instructions irrelevant, would you mind confirming that?

[jamesward]

I think you are right! The version is determined by git now.

[lowasser]

All right, I think I've done it: https://github.com/grpc/grpc-kotlin/releases/tag/v1.4.2 . Hopefully that worked -- I'll leave this issue open for a bit in case there are any problems.

[jamesward]

I think it failed because Maven Central now requires using a generated token for auth for publishing. I think you'll have to work with the team that manages the OSS accounts and get a new token, set it in the env vars, and re-run the failed action.

[credmond-git]

Hello, i still do not see the new release 1.4.2 in Maven Central https://mvnrepository.com/artifact/io.grpc/grpc-kotlin-stub

[sookyeomKim]

Is this library no longer being maintained?

[ejona86]

@lowasser, looking at the release notes, it seems the only change that couldn't be done by downstream users in 1.4.2 is #360. (There were some protoc upgrades, but they seem to not be too important.) Users needing a newer grpc-api can just depend on the newer grpc-java in their own build, right?

[taer]

@lowasser any chance of getting this published to maven central?

[pambrose]

@ejona86 and @lowasser I have tremendous respect for the gRPC team and what they have done with gRPC. Kotlin and gRPC are a fantastic combination and it would be a shame for this repo to be abandoned. Please do not let this happen.

[lowasser]

Just noticed this. Sorry, it's mostly just me, and I do very little with GitHub and Maven. Looking into it now.

[friscoMad]

@lowasser Is there a way to get additional maintainers into the project? Internal or external ones, or a way to raise awareness about this fact, grpc-rust was just announced while grpc-kotlin is dying without any kind of support or updates for years.
And I know that is not your fault, you just happen to be the last one with maintainer access but this project needs some support and I am sure there are people here that can help.

[lowasser]

I am working on getting the appropriate permissions from Sonatype, hopefully with @jamesward 's assistance.