Skip to content

[FLINK-36465] Bump okhttp3 to 4.12.0 #26472

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

r-sidd
Copy link
Contributor

@r-sidd r-sidd commented Apr 17, 2025

What is the purpose of the change

Bump okhttp from 3.14.9 to 4.12.0

Brief change log

Bump okhttp from 3.14.9 to 4.12.0. This will remediate vulnerabilities in underlying dependencies and brings in a lot of bugfixes and features.

Package details:

https://mvnrepository.com/artifact/com.squareup.okhttp3/okhttp/4.12.0

https://mvnrepository.com/artifact/com.squareup.okhttp3/logging-interceptor/4.12.0

Release notes:

https://square.github.io/okhttp/changelogs/upgrading_to_okhttp_4

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

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

@flinkbot
Copy link
Collaborator

flinkbot commented Apr 17, 2025

CI report:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants