grpc-kotlin
grpc-kotlin copied to clipboard
grpc
New release
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.
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?
In James' absence, it's almost certainly just me. I'll try to accomplish this sometime this week.
Let me know if you need any help! Details are at: https://github.com/grpc/grpc-kotlin/blob/master/BUILDING.md#releasing
@jamesward it looks like #480 made step 2 of those instructions irrelevant, would you mind confirming that?
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.
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.
Hello, i still do not see the new release 1.4.2 in Maven Central https://mvnrepository.com/artifact/io.grpc/grpc-kotlin-stub
@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?
@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.
Just noticed this. Sorry, it's mostly just me, and I do very little with GitHub and Maven. Looking into it now.
@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.
I am working on getting the appropriate permissions from Sonatype, hopefully with @jamesward 's assistance.
We automated the process so I don't think you need any special permissions beyond being able to create a tag in this repo. Let me know if you need any help.
It looks like the release GitHub Action failed: https://github.com/grpc/grpc-kotlin/actions But I no longer have access to see the log. So I'm not sure what went wrong. @bshaffer helped set this up so maybe he can help investigate.
@lowasser Have you had any luck publishing the newest release to Maven central? Thanks.
Any chance we could get this pushed? Or maybe published to a different maven repo?
It seems that @lowasser has walked away from this project. @jamesward , do you have any suggestions?
Sorry I'm not able to help with this. Maybe the only option is releasing a fork?
@lowasser and @bshaffer are working through the release.
After fixing some issues, they've gotten publishing to Maven Central mostly working, but there's still validation failures due to integration_testing being added since last release.
Unfortunately in the process version 6f774052d1d6923f8af2e0023886d69949b695ee was also released, which can cause some problems for tooling thinking there is a newer version.
