daniel-packard commented on PR #158: URL: https://github.com/apache/flink-docker/pull/158#issuecomment-1583138454
> You'd have to explicitly upgrade to the next Flink patch version, but that may be a good idea anyway depending on how you deploy Flink. You do _not_ want different processes of Flink using different patch versions, so unless you have safeguards to prevent that in the event that you deploy something at the exact time we do a release, you should maybe consider it. I'm not sure I follow your intent here... are you saying that `1.16.1` -> `1.16.2` is an unsafe version transition to happen automatically? -- 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]
