[Snyk] Upgrade isbot from 5.1.31 to 5.1.32

[nssuwan186-dev]

Snyk has created this PR to upgrade isbot from 5.1.31 to 5.1.32.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released 2 months ago.

Release notes

Package name: isbot

• 5.1.32 - 2025-11-03
  

  Pattern updates (#297)Resolve #296

• 5.1.31 - 2025-09-23
  

  not this again

from isbot GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @nssuwan186-dev, 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, automatically generated by Snyk, updates the isbot dependency to its latest patch version, 5.1.32. This ensures the project incorporates recent pattern updates and bug fixes, contributing to improved maintenance and security posture by keeping dependencies current.

Highlights

• Dependency Upgrade: Upgraded the isbot package from version 5.1.31 to 5.1.32. This update incorporates pattern improvements and resolves specific issues (\AppData\Roaming\uv\python\cpython-3.12.12-windows-x86_64-none\python.exe: can't open file "C:\\代码项目\\valuecell\\python\\python -c 'import pyarrow.util; pyarrow.util.download_tzdata_on_windows()'": [Errno 2] No such file or directory ValueCell-ai/valuecell#297, feat: support OKX trading ValueCell-ai/valuecell#296) within the isbot library.

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 correctly upgrades the isbot dependency from version 5.1.31 to 5.1.32. However, the bun.lock file has not been updated to reflect this change. To ensure the new version of the dependency is actually installed and used in the project, you need to run bun install and commit the resulting changes to the bun.lock file.

[gemini-code-assist]

While package.json is updated, the bun.lock file is missing from this pull request. This means the dependency upgrade won't take effect. Please run bun install to update the lock file and commit the changes.