EmailUtilitites, Enrichment, FileUtilities, Lists, Tools - Remove all usages of items from list method for 1P APIs

[KrishnaSharma06]

EmailUtilitites, Enrichment, FileUtilities, Lists, Tools - Remove all usages of items from list method for 1P APIs

Bug: b/477008157

---

Checklist:

Please ensure you have completed the following items before submitting your PR.
This helps us review your contribution faster and more efficiently.

General Checks:

• I have read and followed the project's contributing.md guide.
• My code follows the project's coding style guidelines.
• I have performed a self-review of my own code.
• My changes do not introduce any new warnings.
• My changes pass all existing tests.
• I have added new tests where appropriate to cover my changes. (If applicable)
• I have updated the documentation where necessary (e.g., README, API docs). (If applicable)

Open-Source Specific Checks:

• My changes do not introduce any Personally Identifiable Information (PII) or sensitive customer data.
• My changes do not expose any internal-only code examples, configurations, or URLs.
• All code examples, comments, and messages are generic and suitable for a public repository.
• I understand that any internal context or sensitive details related to this work are handled separately in internal systems (Buganizer for Google team members).

For Google Team Members and Reviewers Only:

• I have included the Buganizer ID in the PR title or description (e.g., "Internal Buganizer ID: 123456789" or "Related Buganizer: go/buganizer/123456789").
• I have ensured that all internal discussions and PII related to this work remain in Buganizer.
• I have tagged the PR with one or more labels that reflect the pull request purpose.

---

[gemini-code-assist]

Summary of Changes

Hello @KrishnaSharma06, 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 focuses on a comprehensive update of shared dependencies across several key utility packages: EmailUtilities, Enrichment, FileUtilities, Lists, and Tools. The primary driver for these changes, as indicated by the PR title, is to remove specific usages of an "items from list method for 1P APIs," a modification likely contained within the updated integration-testing and tipcommon libraries. The changes propagate these dependency updates, increment the versions of the utility packages themselves, and ensure all associated lock files and release notes are synchronized.

Highlights

• Dependency Updates: The core dependencies, integration-testing and tipcommon libraries, have been consistently updated to version 2.2.24 across all affected utility packages.
• Package Version Bumps: The main utility packages have received version increments: EmailUtilities (44.0 -> 45.0), Enrichment (31.0 -> 32.0), FileUtilities (21.0 -> 22.0), Lists (11.0 -> 12.0), and Tools (73.0 -> 74.0).
• Configuration and Release Note Synchronization: All pyproject.toml and uv.lock files have been updated to reflect the new dependency and package versions, and corresponding entries have been added to the release_notes.yaml files for each utility.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 updates dependencies across several integrations, including EmailUtilities, Enrichment, FileUtilities, Lists, and Tools. The primary change is bumping the versions of tipcommon and integration-testing packages. The version numbers for the integrations themselves have also been incremented, and corresponding release notes have been added.

The changes are straightforward and appear correct. I've added a couple of minor suggestions to add a final newline to two of the release_notes.yaml files, which is a common convention for text files.

[gemini-code-assist]

It's a good practice for text files to end with a newline character. This can prevent issues with certain file processing tools and version control systems.

  ticket_number: '477008157'

[gemini-code-assist]

It's a good practice for text files to end with a newline character. This can prevent issues with certain file processing tools and version control systems.

  ticket_number: '477008157'