chore(master): release 2.10.1

[rubiin]

🤖 I have created a release beep boop

2.10.1 (2026-01-27)

🐛 Bug Fixes

• replace logger warnings with exceptions for better error handling across multiple modules (869d683)
• update geocoding error handling and improve logging in WeatherService (17fc542)

📚 Documentation

• clarify manual installation instructions (#271) (7d4d0cb)

⚙️ Chores

• deps: update all non-major dependencies (#268) (2b0b4f9)
• deps: update all non-major dependencies (#276) (98308a4)

♻️ Code Refactoring

• remove redundant initialization check and update geocode parameters in WeatherService (96255f2)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Summary of Changes

Hello @rubiin, 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.1 of the project. Its primary purpose is to update the project's version number and integrate a recent code refactoring change that improves the WeatherService functionality.

Highlights

• Version Update: The project version has been incremented from 2.10.0 to 2.10.1 across all relevant configuration and manifest files.
• Code Refactoring: A specific code refactoring was included in this release, which involved removing a redundant initialization check and updating geocode parameters within the WeatherService.

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 an automated release for version 2.10.1. The changes correctly update the version number in .release-please-manifest.json and pyproject.toml, and add the corresponding entry to CHANGELOG.md. The changes are appropriate for an automated release and look good.

While not part of the changed files in this PR, I reviewed the code associated with commit 96255f2 mentioned in the changelog and found a couple of minor areas for improvement in services/weather.py:

• The docstring for the _geocode_location method (line 49) states it uses Nominatim, but the implementation actually uses the Open-Meteo geocoding API. This could be updated to avoid confusion.
• In the same method, an error is reported using print on line 63. It would be better to use logger.error for consistency with the logging approach used elsewhere in the file.

Since this file is not part of the diff, I'm mentioning these points here for consideration in a future PR.