chore(deps): update dependency certifi to v2026

[renovate-bot]

This PR contains the following updates:

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

---

Release Notes

certifi/python-certifi (certifi)

v2026.2.25

Compare Source

v2026.1.4

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 updates the certifi Python dependency to its latest version, v2026.2.25, along with its corresponding SHA256 hashes. This change ensures that the project's certificate authority bundle is current, which is crucial for maintaining secure and compatible SSL/TLS connections within the application.

Highlights

• Dependency Update: Updated the certifi Python dependency from version 2025.11.12 to 2026.2.25.
• Security Enhancement: Ensured the project uses the latest CA certificates for enhanced security and compatibility with SSL/TLS connections.

Changelog

• requirements.txt
  • Updated certifi dependency from 2025.11.12 to 2026.2.25
  • Refreshed SHA256 hashes for the updated certifi version

Activity

• Pull request created by renovate-bot to update the certifi dependency.
• Automerge is disabled by configuration, requiring manual merging.
• Release notes for certifi versions v2026.2.25 and v2026.1.4 are provided in the PR description.

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, generated by Renovate, updates the certifi dependency. A critical issue has been identified: both the new version (2026.2.25) and the previous version (2025.11.12) are dates set in the future. Since certifi uses calendar-based versioning, this is highly irregular and points to a potential misconfiguration or security risk that needs immediate attention.

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

[gemini-code-assist]

The version for certifi is being updated to 2026.2.25, which is a date in the future. The certifi package uses calendar versioning (format YYYY.MM.DD), so its version should correspond to a past or current date. Using a future-dated version is a critical issue as it might point to a misconfiguration, a compromised dependency source, or a typosquatting attack. Please correct this to use a valid, recent version of certifi.

[olavloite]

Eh, no....