spuru9 opened a new pull request, #1131:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1131

   ## What is the purpose of the change
   
   Bump the Flink version the operator builds against from `1.20.1` (Jan 2025) 
to `1.20.4` (Apr 2026) — the latest patch in the 1.20 line — to pick up the bug 
and security fixes accumulated across the 1.20.2, 1.20.3 and 1.20.4 releases. 
As a patch bump within the same minor it is source/binary compatible.
   
   `flink.version` is the version the operator *builds* against; runtime 
support for the wider Flink range (2.0/2.1/2.2) is covered separately by the CI 
version matrix, so this does not change which Flink versions the operator can 
deploy.
   
   ## Brief change log
   
     - Bump `flink.version` `1.20.1` -> `1.20.4` in the root `pom.xml`
     - Align the autoscaling example image base from `flink:1.20.1-java17` to 
`flink:1.20.4-java17`
     - Align the e2e batch-job examples jar from `1.20.1` to `1.20.4`
     - Update the `flink-metrics-otel` comment that referenced the pinned 
`flink.version`
   
   ## Verifying this change
   
   This change is already covered by existing tests / CI. Locally verified that 
`mvn clean install javadoc:javadoc -Pgenerate-docs` builds all modules 
successfully against Flink 1.20.4.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **yes** (Flink 
`1.20.1` -> `1.20.4`, patch upgrade)
     - The public API, i.e., is any changes to the `CustomResourceDescriptors`: 
no
     - Core observer or reconciler logic that is regularly executed: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to