Skip to content

Bump fickling to 0.1.6 in api lockfile (Vibe Kanban)#30494

Closed
laipz8200 wants to merge 1 commit into
mainfrom
vk/0d2b-cve-2025-67747
Closed

Bump fickling to 0.1.6 in api lockfile (Vibe Kanban)#30494
laipz8200 wants to merge 1 commit into
mainfrom
vk/0d2b-cve-2025-67747

Conversation

@laipz8200

@laipz8200 laipz8200 commented Jan 4, 2026

Copy link
Copy Markdown
Member

What

  • Updated api/uv.lock to bump transitive fickling from 0.1.5 to 0.1.6.

Why

  • Address CVE-2025-67747 flagged by Docker Scout; the fix requires fickling>=0.1.6.

Details

  • Dependency chain: dify-api -> weave -> polyfile-weave -> fickling.
  • Lockfile entries were refreshed with the new sdist/wheel URLs and hashes.

Testing

  • Not run (lockfile-only change).

This PR was written using Vibe Kanban

- 依赖来源:`dify-api` -> `weave` -> `polyfile-weave` -> `fickling`(仅在锁文件中,代码里无直接引用)
- 已更新:`api/uv.lock`(`fickling` 0.1.5 -> 0.1.6)

Tests not run(仅更新锁文件)。

如果你希望在 `pyproject.toml` 中显式锁定 `fickling>=0.1.6` 以防未来回退,告诉我我可以加上。
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @laipz8200, I'm Gemini Code Assist1! 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 enhancing the security posture of the application by updating a critical dependency. It specifically targets CVE-2025-67747, ensuring that the dify-api component, which relies on the fickling package, is running a patched version to prevent potential exploits.

Highlights

  • Security Vulnerability Resolution: This pull request addresses CVE-2025-67747 by upgrading the fickling package to version 0.1.6 to mitigate the identified vulnerability.
  • Dependency Update: The fickling dependency, used by dify-api, has been updated from version 0.1.5 to 0.1.6 within the api/uv.lock file.

🧠 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.

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.

@laipz8200 laipz8200 closed this Jan 4, 2026
@laipz8200 laipz8200 changed the title CVE-2025-67747 (vibe-kanban) Bump fickling to 0.1.6 in api lockfile (Vibe Kanban) Jan 4, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

本次变更旨在修复 fickling 包中的安全漏洞 CVE-2025-67747。您通过更新 api/uv.lock 文件,成功将 fickling 的版本从 0.1.5 升级到了 0.1.6。这个改动是正确且必要的,有效地解决了该安全问题。做得很好!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant