chore(deps): update dependency certifi to v2025.11.12

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
certifi	==2025.10.5 → ==2025.11.12

---

Release Notes

certifi/python-certifi (certifi)

v2025.11.12

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[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 focuses on maintaining the project's security and compatibility by updating the certifi dependency to its most recent version. This update incorporates the latest collection of trusted root certificates, which is essential for secure communication over the internet, particularly for applications making HTTPS requests.

Highlights

• Dependency Update: Updated the certifi package from version 2025.10.5 to 2025.11.12.
• Security Enhancement: Ensured the project uses the latest root certificate authority bundle for improved SSL/TLS security.

Changelog

• requirements.txt
  • Updated the certifi dependency version from 2025.10.5 to 2025.11.12.
  • Refreshed the SHA256 hash values corresponding to the new certifi version to ensure integrity.

Activity

• The pull request was automatically generated by Mend Renovate to update the certifi dependency.
• Automerge is currently disabled, requiring a manual merge once satisfied with the changes.
• The PR is configured to rebase or retry automatically if conflicts arise or if manually triggered.

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 the certifi dependency from 2025.10.5 to 2025.11.12. The change in requirements.txt correctly updates the version and its associated hashes. This is a routine dependency update and appears to be correct.

_{Note: Security Review has been skipped due to the limited scope of the PR.}