chore(deps): update python docker tag to v3.14.3

[talkiq-ops]

This PR contains the following updates:

Package	Type	Update	Change
python	docker	patch	3.14.2 → 3.14.3

---

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.

[gemini-code-assist]

Summary of Changes

Hello @talkiq-ops, 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 automates the process of keeping the project's Python Docker image dependency up-to-date. By updating to the latest patch version, it ensures that the continuous integration environment benefits from the most recent bug fixes and minor improvements without introducing breaking changes.

Highlights

• Python Docker Image Update: The Python Docker image used in the CI/CD configuration has been updated from version 3.14.2 to 3.14.3.
• Configuration File Change: This update is reflected in the .circleci/config.yml file, specifically within the executors.python.docker section.

🧠 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

• .circleci/config.yml
  • Updated the Python Docker image tag from python:3.14.2 to python:3.14.3.

Activity

• This pull request was automatically generated by Renovate Bot.
• Automerge is enabled for this PR, allowing it to merge automatically once all checks pass.
• Rebasing is configured to occur when the PR is behind the base branch 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. ↩

[github-actions]

Approved 👍

[gemini-code-assist]

Code Review

This pull request updates the Python Docker image tag in .circleci/config.yml from 3.14.2 to 3.14.3. This is a straightforward dependency update, and the change aligns with the pull request description. No specific issues or areas for improvement were identified in this change.