Pin ai-edge-litert version to fix CI

[abheesht17]

The only version of ai-edge-litert which works with TF 2.20.0 is 1.3.0. Pinning the version for now, and added TODO statements for when we upgrade TF.

Created an issue to track this: #21914

[gemini-code-assist]

Summary of Changes

Hello @abheesht17, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a critical CI failure by pinning the ai-edge-litert dependency to version 1.3.0, which is the only version currently compatible with TensorFlow 2.20.0. To maintain immediate stability, an LSTM model test case that was incompatible with this specific ai-edge-litert version has been temporarily commented out. The changes include clear TODO markers to facilitate future dependency upgrades and the re-introduction of the LSTM test, ensuring the project remains functional while planning for future enhancements.

Highlights

• Dependency Pinning: The ai-edge-litert package has been explicitly pinned to version 1.3.0 in requirements.txt to ensure compatibility with TensorFlow 2.20.0.
• CI Stability: This change directly addresses and fixes continuous integration failures that were caused by an incompatibility between ai-edge-litert and the current TensorFlow version.
• Test Suite Adjustment: The lstm model type test case in litert_test.py has been temporarily disabled, as it is not compatible with the pinned ai-edge-litert==1.3.0 version.
• Future Work: Explicit TODO comments have been added in both requirements.txt and litert_test.py to guide future upgrades of ai-edge-litert and TensorFlow, and to re-enable the lstm test when compatibility is restored.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly pins the ai-edge-litert version to 1.3.0 to resolve a CI failure with TensorFlow 2.20.0. As a necessary consequence, the LSTM model tests for LiteRT export are temporarily disabled. The changes are well-commented with TODOs explaining the temporary nature of the fix. My feedback focuses on making these TODO comments more actionable by linking them to a tracking issue, which will improve long-term maintainability and ensure these temporary measures are revisited when the dependencies are updated.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.40%. Comparing base (f0a48a6) to head (44cb287).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #21912      +/-   ##
==========================================
+ Coverage   76.30%   82.40%   +6.10%     
==========================================
  Files         580      580              
  Lines       60029    60031       +2     
  Branches     9432     9433       +1     
==========================================
+ Hits        45803    49470    +3667     
+ Misses      11750     8141    -3609     
+ Partials     2476     2420      -56     

Flag	Coverage Δ
keras	82.22% <ø> (+6.05%)	⬆️
keras-jax	62.12% <ø> (+<0.01%)	⬆️
keras-numpy	57.32% <ø> (+<0.01%)	⬆️
keras-openvino	34.30% <ø> (-0.01%)	⬇️
keras-tensorflow	64.30% <ø> (?)
keras-torch	63.22% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.