Protobuf 3.25 End of Life: Java 3.25.x Support Ends March 31, 2027
Protobuf 3.25 reaches end of support on March 31, 2027 for Java (protobuf-java 3.25.x), the only language where the 25.x release line is still supported; for Python 4.25.x, C++ 4.25.x, PHP 3.25.x and Ruby 3.25.x, support ended on March 31, 2025. The dates are from the Version Support page on protobuf.dev, which has a separate table for each language. One Protobuf release has a different major version number in each language: protoc 25.x is Java 3.25.x, Python 4.25.x and C++ 4.25.x. The page lists protoc 25.x under Maintenance Only and adds the words "for Java". Java 4.x is the Active line, and its End of support date is March 31, 2028.
Key Dates at a Glance
- Protobuf Java 3.x (3.25.x, protoc 25.x): first 3.25 release 2023-11-01; End of support 2027-03-31 (Maintenance)
- Protobuf Java 4.x (protoc 26.x and later): released 2024-03-13; End of support 2028-03-31 (Active)
- Protobuf Java 5.x: projected release Q1 2027; End of support 2029-03-31 (Future)
- Protobuf Python 4.x (4.25.x, protoc 25.x): End of support 2025-03-31 (End of Life)
- Protobuf C++ 4.x (4.25.x, protoc 25.x): End of support 2025-03-31 (End of Life)
- Protobuf PHP 3.x and Ruby 3.x (3.25.x, protoc 25.x): End of support 2025-03-31 (End of Life)
- Protobuf Python 6.x and C++ 6.x (protoc 30.x to 33.x): End of support 2027-03-31 (Maintenance)
Protobuf 25.x in each language
Protobuf releases are numbered minor.point, for example 25.3. Each language runtime uses the same minor and point with its own major version in front. That is why the release people call "protobuf 3.25" is version 4.25 in Python and C++. The table shows the 25.x release line as protobuf.dev lists it for each language.
| Language | Runtime version for protoc 25.x | Major line on protobuf.dev | End of support | Status on protobuf.dev |
|---|---|---|---|---|
| Java | 3.25.x | 3.x (protoc 21.x-25.x) | March 31, 2027 | Maintenance |
| Python | 4.25.x | 4.x (protoc 21.x-25.x) | March 31, 2025 | End of Life |
| C++ | 4.25.x | 4.x (protoc 22.x-25.x) | March 31, 2025 | End of Life |
| PHP | 3.25.x | 3.x (protoc 21.x-25.x) | March 31, 2025 | End of Life |
| Ruby | 3.25.x | 3.x (protoc 21.x-25.x) | March 31, 2025 | End of Life |
| Objective-C | 3.25.x | 3.x (protoc 21.x-29.x) | March 31, 2026 | End of Life |
| C# | 3.25.x | 3.x (protoc 21.x+) | TBD | 3.x is Active; 3.25 is not its newest minor |
Status words, protoc ranges and TBD are protobuf.dev's own. For C# and Objective-C, Protobuf 26.0 was not a new major version: 3.25 was followed by 3.26 in the same 3.x line. The page's rule is that a new minor version immediately ends support for the previous minor version, so 3.25.x is not a supported minor in either language. Go is left out: its 1.x versions did not share the 25.x number, and the page says only the current Go release is supported.
The first 3.25 release, Protobuf 25.0, was published on November 1, 2023. Java 3.25.x has been in Maintenance since Protobuf 26.0 started the Java 4.x line on March 13, 2024. Patch releases still arrive: the most recent 25.x release on the project's GitHub releases page was published on March 25, 2026.
Every major line by language
This table lists every major line protobuf.dev shows for each language, with the End of support date the page prints. One row is left out: C++ 3.x, which the page lists as End of Life with an earlier date than any row here.
| Language | Major line | protoc releases | End of support | Status on protobuf.dev |
|---|---|---|---|---|
| Java | 3.x | 21.x-25.x | March 31, 2027 | Maintenance |
| Java | 4.x | 26.x+ | March 31, 2028 | Active |
| Java | 5.x | not released | March 31, 2029 | Future |
| Python | 4.x | 21.x-25.x | March 31, 2025 | End of Life |
| Python | 5.x | 26.x-29.x | March 31, 2026 | End of Life |
| Python | 6.x | 30.x-33.x | March 31, 2027 | Maintenance |
| Python | 7.x | 34.x+ | TBD | Active |
| C++ | 4.x | 22.x-25.x | March 31, 2025 | End of Life |
| C++ | 5.x | 26.x-29.x | March 31, 2026 | End of Life |
| C++ | 6.x | 30.x-33.x | March 31, 2027 | Maintenance |
| C++ | 7.x | 34.x+ | TBD | Active |
| PHP | 3.x | 21.x-25.x | March 31, 2025 | End of Life |
| PHP | 4.x | 26.x-33.x | March 31, 2026 | Maintenance (see the note below) |
| PHP | 5.x | 34.x+ | TBD | Active |
| Ruby | 3.x | 21.x-25.x | March 31, 2025 | End of Life |
| Ruby | 4.x | 26.x+ | TBD | Active |
| Objective-C | 3.x | 21.x-29.x | March 31, 2026 | End of Life |
| Objective-C | 4.x | 30.x-33.x | March 31, 2027 | Maintenance |
| Objective-C | 5.x | 34.x-37.x | Q4 2027 | Active |
| C# | 3.x | 21.x+ | TBD | Active |
| Go | 1.x | 36.x+ | TBD | Active |
Three things in this table need a second look on protobuf.dev. The PHP 4.x row prints an End of support date of March 31, 2026, yet the same page still lists PHP 4.33.x under Maintenance Only; the two do not agree, and we show both as printed. The page says support for Objective-C will be dropped as of the 38.x release, and it prints only a quarter, Q4 2027, for Objective-C 5.x. Java 5.x is a projected release: the page gives it a projected release date of Q1 2027, printed with an asterisk like the Java 3.x date.
The support rule behind the dates
protobuf.dev states the rule in three sentences. The project always supports the most recent release. A new minor version immediately ends support for the previous minor version. A new major version ends support for the previous major version four quarters later.
- Active. Minor and patch releases with new features, compatible changes and bug fixes. Java 4.x is the Active line for Java.
- Maintenance. Patch releases with critical bug and security vulnerability fixes. Java 3.25.x is in this phase until March 31, 2027.
- End of Life. The release is unsupported, and the page tells users to upgrade to a supported release. Python 4.25.x and C++ 4.25.x are here.
- Future. A projected release, shown for planning purposes. Java 5.x is listed this way.
Java is the exception to the four-quarter rule. The page says the maintenance support window for the Protobuf Java 3.x release line is 36 months instead of the typical 12 months. That is why Java 3.25.x is still in Maintenance while the 25.x release line is End of Life for Python, C++, PHP and Ruby.
The minor-version rule matters for Java too. Only 3.25.x is in Maintenance. Java 3.21 through 3.24 are earlier minors of the same 3.x line, and each one left support when the next minor was released. Our Protobuf 3.0 to 3.24 page covers them.
What is newer and supported
Java 4.x is the Active line. It began with Protobuf 26.0, released on March 13, 2024, and its End of support date is March 31, 2028. The project releases quarterly and targets major releases, the ones with breaking changes, for the first quarter of a year.
protobuf.dev lists Protobuf Java 5.x as Future, with a projected release date of Q1 2027 and End of support March 31, 2029. Those are plans, and the page says future plans might change. They fit the rule above: a Java 5.x release would start the four quarters that end with the Java 4.x End of support date.
For the other languages, the Active lines are Python 7.x, C++ 7.x, PHP 5.x, Ruby 4.x, Objective-C 5.x and C# 3.x. Python 6.x and C++ 6.x are in Maintenance, and the End of support date for both is March 31, 2027, the same day as Java 3.25.x.
What a team on protobuf 3.25 should plan
The steps below use the Version Support page and the project's Cross-Version Runtime Guarantee.
- Find the runtime you ship. For Java it is the
com.google.protobuf:protobuf-javaartifact, andmvn dependency:tree -Dincludes=com.google.protobufshows the version Maven resolves. For Python it is theprotobufpackage, andpip show protobufprints its version. Protobuf often arrives through another library, so check the resolved version, not only the one you declared. - On Java 3.25.x, take the newest 3.25.x patch release. Maintenance fixes ship only as patch releases of 3.25.x.
- On Java 3.24 or older, move to 3.25.x first. Those minors are not in Maintenance. Within one major runtime version, the project says generated code from an older protoc runs on a newer runtime.
- Plan the move to Java 4.x before March 31, 2027. The guarantee says code generated for a major version is supported by runtimes of that major version and the next one. Its own example is Java code generated by 3.0.0, which works with runtimes up to 4.x.y. The reverse is never allowed: generated code must not be paired with a runtime older than the protoc that generated it. The project recommends regenerating code with every release update. A major release can change APIs in ways that need code changes, so read the Protobuf 26.0 release notes first.
- Regenerate before Java 5.x. By the same guarantee, Java code generated by a 3.x release is not supported on 5.x runtimes. Code generated by a Java 4.x release (protoc 26.x or later) is.
- Keep one major version in a process. The guarantee says coexistence of multiple major versions in the same process is not supported. Check every library that brings its own protobuf-java.
- On Python 4.25.x, C++ 4.25.x, PHP 3.25.x or Ruby 3.25.x, move now. These are End of Life on protobuf.dev. The Active lines are Python 7.x, C++ 7.x, PHP 5.x and Ruby 4.x. C++ requires an exact match between the generated code version and the runtime version. For Python, the guarantee says that as of 6.32.0 all generated code since 3.20.0 will be supported until at least 8.x.y.
- If you cannot move before March 31, 2027: stay on the newest 3.25.x patch release and record the risk. protobuf.dev's status for a release past its End of support date is End of Life, which it defines as unsupported.
The Stack Scanner reads a pom.xml or build.gradle and reports the end-of-life dates of the packages it recognizes, protobuf-java among them. The EOL Checker looks up one product and version.
Frequently Asked Questions
When does protobuf 3.25 reach end of support?
March 31, 2027, for Java only. protobuf.dev lists Protobuf Java 3.x, whose supported minor is 3.25.x, as Maintenance with End of support March 31, 2027. For Python 4.25.x, C++ 4.25.x, PHP 3.25.x and Ruby 3.25.x, support ended on March 31, 2025.
Is protobuf-java 3.25.x still supported?
Yes, in Maintenance. protobuf.dev defines Maintenance as patch releases with critical bug and security vulnerability fixes. Java 3.25.x is the only 3.x minor in Maintenance, and its End of support date is March 31, 2027.
Is Python protobuf 4.25.x still supported?
No. protobuf.dev lists Protobuf Python 4.x as End of Life, with End of support March 31, 2025. Python 6.x is in Maintenance with End of support March 31, 2027, and Python 7.x is Active.
When does protobuf-java 4.x reach end of support?
March 31, 2028. Java 4.x is the Active line. It began with Protobuf 26.0, released on March 13, 2024.
When will protobuf-java 5.x be released?
protobuf.dev lists Protobuf Java 5.x as Future, with a projected release date of Q1 2027 and End of support March 31, 2029. The page says future plans might change.
Which protoc version matches protobuf-java 3.25.x?
protoc 25.x. One Protobuf release has a different major version number in each language: protoc 25.x is Java 3.25.x, Python 4.25.x and C++ 4.25.x, and it is 3.25.x in C#, Objective-C, PHP and Ruby.
Why is protobuf 25.x supported longer for Java than for other languages?
protobuf.dev says the maintenance support window for the Protobuf Java 3.x release line is 36 months instead of the typical 12 months. The usual rule is that a new major version ends support for the previous major version four quarters later.
Related
- Protocol Buffers — the Java runtime's versions, live status and EOL Risk Score
- Java end-of-life dates by vendor — the JDK under protobuf-java
- Python end of life — the interpreter under the Python runtime
- EOL Checker and Stack Scanner
- How we verify our dates