[FLINK-36465] Bump okhttp from 3.14.9 to 4.12.0
What is the purpose of the change
[FLINK-36465] 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: don't know
- 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
CI report:
- 0e4aa16b10321b3b6c2e991dce484895a28be99a Azure: FAILURE
Bot commands
The @flinkbot bot supports the following commands:@flinkbot run azurere-run the last Azure build
This PR is being marked as stale since it has not had any activity in the last 90 days. If you would like to keep this PR alive, please leave a comment asking for a review. If the PR has merge conflicts, update it with the latest from the base branch.
If you are having difficulty finding a reviewer, please reach out to the community, contact details can be found here: https://flink.apache.org/what-is-flink/community/
If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.