Upgrade TensorFlow to version 2.11.* #651
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Kudos, SonarCloud Quality Gate passed!
|
Codecov ReportBase: 99.55% // Head: 99.55% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #651 +/- ##
=======================================
Coverage 99.55% 99.55%
=======================================
Files 87 87
Lines 6006 6006
=======================================
Hits 5979 5979
Misses 27 27 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
On second thought, I think this is fine and basically a minimal upgrade, I'll merge it as is. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are currently using TensorFlow 2.9.1, which has reported vulnerabilities. Also dependabot is complaining about them.
It would be trivial to upgrade to 2.9.3, where those issues have been fixed.
But instead, I tested upgrading directly to 2.11.0. Everything seems to work fine with this new version. I also tested a small model that was trained on 2.9.1, before the upgrade, and it worked perfectly well.
I pinned this as
2.11.*so that upgrading to patch releases is allowed in the future.