potiuk commented on PR #30487: URL: https://github.com/apache/airflow/pull/30487#issuecomment-1516073030
FYI. MySQL does not really collaboarate. They released a new version of `mysql-connector-python `8.0.33` two days ago, but it still has < 3.20 limit on protobuf. Also, I got this - completely useless and apparently automatically generated response today to my issue: > Here are the general steps to upgrade to a newer version of protobuf: > > Check compatibility: Before upgrading to a newer version of protobuf, check if the new version is compatible with your current codebase and other dependencies. Review the release notes and documentation to see if there are any changes or deprecations that could affect your code. > > Update protobuf files: If you have any custom protobuf files, update them to the latest version. You can use the protoc compiler to generate updated code from the new protobuf files. > > Update dependencies: If you are using a language-specific implementation of protobuf (such as the Python protobuf package or the Java protobuf library), update your dependencies to the latest version. > > Update code: Update your code to use the new version of protobuf. This may involve updating method signatures, changing import statements, and updating serialization/deserialization code. > > Test thoroughly: After making the updates, test your code thoroughly to ensure that everything works as expected. Test both positive and negative cases to ensure that there are no regressions or new issues introduced by the upgrade. > > Roll back if necessary: If you encounter any issues or compatibility problems, be prepared to roll back to the previous version of protobuf until the issues can be resolved. > > By following these steps, you should be able to successfully upgrade to a newer version of protobuf while minimizing the risk of compatibility issues and regressions. I answered appropriately : https://forums.mysql.com/read.php?50,708413,708803#msg-708803 -- 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]
