chore(master): release 2.10.2

[rubiin]

🤖 I have created a release beep boop

2.10.2 (2026-03-16)

⚙️ Chores

• deps: update dependency ijson to v3.5.0 (#285) (4ca37b3)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Summary of Changes

Hello, 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 represents an automated release for version 2.10.2 of the Tsumiki project. The primary change included in this release is an update to the ijson dependency, ensuring the project utilizes the latest stable version of this library.

Highlights

• New Release: This pull request introduces version 2.10.2 of the project, an automated release generated by Release Please.
• Dependency Update: The ijson dependency has been updated to version 3.5.0 as part of this release.

🧠 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.

Changelog

• .release-please-manifest.json
  • Updated the recorded project version to 2.10.2.
• CHANGELOG.md
  • Added a new section for version 2.10.2, detailing the ijson dependency update.
  • Included a link to the compare view for the new version.
  • Documented the chore for updating ijson to v3.5.0.
• pyproject.toml
  • Updated the project's version field to 2.10.2.

Activity

• The pull request was automatically generated by Release Please.
• It includes a chore to update the ijson dependency to v3.5.0, as noted in the changelog.

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 is for the release of version 2.10.2. The version bumps in the manifest and project files are correct. However, I've noticed that the release date in the CHANGELOG.md is set to a future date. This appears to be a recurring issue with the automated release process and should be investigated.

[gemini-code-assist]

The release date is set to a future date (2026-03-02). This seems to be a recurring issue with recent releases, as previous entries also have future dates. Please check the configuration of the release automation tool to ensure correct dates are used.