Skip to content

Commit 6cd724c

Browse files
Protocol Buffer TeamLogofile
authored andcommitted
This changes includes the following:
* Adds a news entry for end of Ruby 2.7 support * Adds information to the proto3 topic about using proto messages for `key_type` PiperOrigin-RevId: 612841114 Change-Id: I8d0c2aab7e7bf6732456ac65c749ef2b9ecbeb8d
1 parent 9e0d9fc commit 6cd724c

File tree

3 files changed

+18
-2
lines changed

3 files changed

+18
-2
lines changed

content/news/2024-02-27.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
+++
2+
title = "Changes Announced on February 27, 2024"
3+
linkTitle = "February 27, 2024"
4+
toc_hide = "true"
5+
description = "Changes announced for Protocol Buffers on February 27, 2024."
6+
type = "docs"
7+
+++
8+
9+
## Dropping Ruby 2.7 Support
10+
11+
As per our official
12+
[Ruby support policy](https://cloud.google.com/ruby/getting-started/supported-ruby-versions),
13+
we will be dropping support for Ruby 2.7 and lower on March 31, 2024. The
14+
minimum supported Ruby version will be 3.0.

content/news/_index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ per-release topics, as some content is not tied to a version.
1616
The following news topics provide information in the reverse order in which it
1717
was released.
1818

19+
* [February 27, 2024](/news/2024-02-05) - Dropping
20+
support for older versions of Ruby
1921
* [February 5, 2024](/news/2024-02-05) - Breaking
2022
changes in Java, C++, and Python in the 26.x line.
2123
* [January 31, 2024](/news/2024-01-31) - Breaking

content/programming-guides/proto3.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1052,8 +1052,8 @@ map<key_type, value_type> map_field = N;
10521052

10531053
...where the `key_type` can be any integral or string type (so, any
10541054
[scalar](#scalar) type except for floating point types and `bytes`). Note that
1055-
enum is not a valid `key_type`. The `value_type` can be any type except another
1056-
map.
1055+
neither enum nor proto messages are valid for `key_type`.
1056+
The `value_type` can be any type except another map.
10571057

10581058
So, for example, if you wanted to create a map of projects where each `Project`
10591059
message is associated with a string key, you could define it like this:

0 commit comments

Comments
 (0)