-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README.md: Correct gradle protobuf reference from 3.22.3 to 3.24.0 #10772
Conversation
1. The bump to `3.23.4` was incorrectly done to the master README in grpc#10359. 2. This was reverted in grpc#10430. 3. 1.58.0 release updated it to `3.23.4` for maven, but kept at `3.22.3` for gradle (75af7ab).
@YifeiZhuang ah, good catch. Let me fix it then. |
The latest is |
@YifeiZhuang Yes, I've upgraded protobuf to 3.25.1 a few weeks ago, but README.md for the new versions is updated during the release procedure. See notes in PR description:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On I see, so you will update protobuf version to the 1.61 branch later on.
I think it is fine to just update the newest version to master branch README.md before release procedure on the RELEASING.md so that it saves you one step. But either way.
@YifeiZhuang no - this line is updated after the tag is published, so README.md would be broken for 2 weeks between the branch cut and the release. But thanks for the review! |
…rpc#10772) 1. The bump to `3.23.4` was incorrectly done to the master README in grpc#10359. 2. This was reverted in grpc#10430. 3. Then protobuf was upgraded again in 1.58.0, from `3.23.4` to `3.24.0` (f8baa9c) 4. 1.58.0 release updated it to `3.24.0` for maven, but kept at `3.22.3` for gradle (75af7ab).
…rpc#10772) 1. The bump to `3.23.4` was incorrectly done to the master README in grpc#10359. 2. This was reverted in grpc#10430. 3. Then protobuf was upgraded again in 1.58.0, from `3.23.4` to `3.24.0` (f8baa9c) 4. 1.58.0 release updated it to `3.24.0` for maven, but kept at `3.22.3` for gradle (75af7ab).
…rpc#10772) 1. The bump to `3.23.4` was incorrectly done to the master README in grpc#10359. 2. This was reverted in grpc#10430. 3. Then protobuf was upgraded again in 1.58.0, from `3.23.4` to `3.24.0` (f8baa9c) 4. 1.58.0 release updated it to `3.24.0` for maven, but kept at `3.22.3` for gradle (75af7ab).
…10772) (#10788) 1. The bump to `3.23.4` was incorrectly done to the master README in #10359. 2. This was reverted in #10430. 3. Then protobuf was upgraded again in 1.58.0, from `3.23.4` to `3.24.0` (f8baa9c) 4. 1.58.0 release updated it to `3.24.0` for maven, but kept at `3.22.3` for gradle (75af7ab).
…10772) (#10789) 1. The bump to `3.23.4` was incorrectly done to the master README in #10359. 2. This was reverted in #10430. 3. Then protobuf was upgraded again in 1.58.0, from `3.23.4` to `3.24.0` (f8baa9c) 4. 1.58.0 release updated it to `3.24.0` for maven, but kept at `3.22.3` for gradle (75af7ab).
…10772) (#10790) 1. The bump to `3.23.4` was incorrectly done to the master README in #10359. 2. This was reverted in #10430. 3. Then protobuf was upgraded again in 1.58.0, from `3.23.4` to `3.24.0` (f8baa9c) 4. 1.58.0 release updated it to `3.24.0` for maven, but kept at `3.22.3` for gradle (75af7ab).
3.23.4
was incorrectly done to the master README in Upgrade dependencies post v1.57.x branch cut #10359.3.23.4
to3.24.0
(f8baa9c)3.24.0
for maven, but kept at3.22.3
for gradle (75af7ab).Notes: