> Are we unblocked to upgrade things like errorprone now? Yeah I think so. We have already started upgrading gradle plugins (e.g. checkerframework-gradle-plugin in #35624). Errorprone is also in plan.
Thanks, Yi On Thu, Jul 17, 2025 at 5:07 PM Kenneth Knowles <k...@apache.org> wrote: > Awesome! > > Are we unblocked to upgrade things like errorprone now? > > Kenn > > On Wed, Jul 16, 2025 at 2:37 PM XQ Hu via dev <dev@beam.apache.org> wrote: > >> Thank you, Yi! >> >> On Wed, Jul 16, 2025 at 5:02 PM Ahmed Abualsaud via dev < >> dev@beam.apache.org> wrote: >> >>> Amazing, thank you Yi! >>> >>> On Wed, Jul 16, 2025 at 4:59 PM Yi Hu via dev <dev@beam.apache.org> >>> wrote: >>> >>>> Hi Beam Developers, >>>> >>>> As part of Java8 deprecation [1], Beam repo now requires Java11+ to >>>> build jars from Beam repository sources. >>>> >>>> * What's affected: >>>> >>>> Commit [2] upgraded certain Gradle plugins that dropped Java 8 support. >>>> As a result, build Beam using Gradle now requires Java11+ in JAVA_HOME or >>>> PATH. >>>> >>>> * What's not affected: >>>> >>>> The byte code compatibility of Beam Java artifacts aren't changed. It's >>>> still on Java 8 until Beam 3.0, as planned. >>>> >>>> Users can still use Java 8 to build their own pipelines, though it's >>>> deprecated since Beam 2.66.0 [3]. Prior to that, individual optional >>>> modules (e.g. IOs) may drop Java 8 support earlier due to upstream >>>> dependency support status. For example, DebeziumIO will require Java17+ >>>> since Beam 2.67.0 ([4]). >>>> >>>> Thanks for your attention! >>>> >>>> [1] https://github.com/apache/beam/issues/31678 >>>> >>>> [2] >>>> https://github.com/apache/beam/commit/01768c3787bf16c0c6d3cc0d377e81b0ee4f22d0 >>>> >>>> [3] https://github.com/apache/beam/pull/35064 >>>> >>>> [4] https://github.com/apache/beam/issues/34747 >>>> -- >>>> >>>> Yi Hu, (he/him/his) >>>> >>>> Software Engineer >>>> >>>> >>>>
