Skip to content

[FLINK-39829][build] Bump scala to 2.12.21#28299

Merged
snuyanzin merged 1 commit into
apache:masterfrom
snuyanzin:flink39829
Jun 3, 2026
Merged

[FLINK-39829][build] Bump scala to 2.12.21#28299
snuyanzin merged 1 commit into
apache:masterfrom
snuyanzin:flink39829

Conversation

@snuyanzin
Copy link
Copy Markdown
Contributor

@snuyanzin snuyanzin commented Jun 3, 2026

What is the purpose of the change

Bumping scala to 2.12.21
as based on https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html
it is better to have 2.12.21 for the case of java 25
also it is binary compatible (as mentioned at https://github.com/scala/scala/releases/tag/v2.12.21)

Brief change log

pom, NOTICE

Verifying this change

existing tests

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (yes )
  • The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no )
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
  • The S3 file system connector: (no )

Documentation

  • Does this pull request introduce a new feature? ( no)
  • If yes, how is the feature documented? (not applicable)

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

@flinkbot
Copy link
Copy Markdown
Collaborator

flinkbot commented Jun 3, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

Copy link
Copy Markdown
Contributor

@MartijnVisser MartijnVisser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did a check on the Scala upgrade and I think this is safe to merge, because:

  1. The Scala release notes state ""Scala 2.12.21 is binary-compatible with the whole Scala 2.12 series".
  2. The reason why Flink was pinned to 2.12.7 for such a long time was because 2.12.8 broke closure/lambda serialization, and that surface lived in the Scala DataStream/DataSet API in module flink-scala. We don't have that anymore since Flink 2.0. The Scala usage we have are flink-table-planner internals and the table-api-scala part, which has no user-facing savepoint/closure serializers.

So LGTM, assuming CI passes of course

Copy link
Copy Markdown
Contributor

@raminqaf raminqaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions github-actions Bot added the community-reviewed PR has been reviewed by the community. label Jun 3, 2026
@snuyanzin
Copy link
Copy Markdown
Contributor Author

now it is green, merging
thanks for taking a look

@snuyanzin snuyanzin merged commit b63688e into apache:master Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-reviewed PR has been reviewed by the community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants