chore: update deps

[hyoban]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran make lint and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods

[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 a comprehensive update of the frontend dependencies, aiming to keep the project's technology stack current. By upgrading key libraries such as Next.js, Tanstack Query, and Storybook, the project benefits from the latest features, performance improvements, and security patches. Additionally, a minor but important configuration change was made to Tailwind CSS to streamline its processing by ignoring test-related files.

Highlights

• Dependency Updates: Upgraded several core frontend dependencies, including @orpc/* packages, @tanstack/react-query, Next.js, and various Storybook-related libraries, to their latest versions.
• Development Tooling Enhancements: Updated TypeScript native preview, knip, and @tanstack/eslint-plugin-query to newer versions, ensuring the use of the latest development tools.
• Tailwind CSS Configuration Adjustment: Modified the Tailwind CSS configuration to explicitly exclude spec and test files from being processed, optimizing build performance and preventing unintended styling.

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

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

[Copilot]

Pull request overview

Updates the web workspace’s dependencies and related configuration to keep the frontend toolchain current and reduce Tailwind’s content scanning scope.

Changes:

• Bumped several frontend dependencies (Next.js, Storybook, TanStack Query, ORPC, etc.) and regenerated pnpm-lock.yaml.
• Updated Tailwind content globs to exclude *.spec.* / *.test.* files from scanning.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
web/tailwind.config.js	Excludes test/spec files from Tailwind content scanning.
web/package.json	Updates dependency and devDependency versions (Next.js, Storybook, ORPC, TanStack Query, tooling).
web/pnpm-lock.yaml	Lockfile refresh reflecting the updated dependency graph.

Files not reviewed (1)

• web/pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

This pull request updates several dependencies. My review focuses on the implications of these updates. I've identified a potentially incorrect version for a development dependency that could cause issues. Additionally, the lock file now flags several transitive dependencies as deprecated, which presents an opportunity to reduce technical debt. Addressing these points will improve the stability and maintainability of the project.