chore(deps): 패키지 의존성 업데이트

[ohprettyhak]

✅ 작업 내용

• 메이저 버전을 제외하고, 사용되는 패키지 의존성을 업데이트 했어요.

[gemini-code-assist]

Summary of Changes

Hello @ohprettyhak, 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 routine maintenance task: updating various package dependencies across the monorepo. The changes span multiple applications and shared packages, primarily involving minor and patch version bumps. The intent is to keep the project's dependencies current, leveraging the latest bug fixes, performance enhancements, and non-breaking features from these libraries, thereby improving overall stability and developer experience.

Highlights

• Core Framework Updates: The next framework and related packages like @next/third-parties and @next/eslint-plugin-next have been updated to version 15.4.3 across the manager and spectator applications, as well as the api and eslint-config packages. This brings the project up to the latest minor release of Next.js.
• State Management and Data Fetching Libraries: react-hook-form was updated from 7.60.0 to 7.61.0 in apps/manager and packages/ui. Additionally, @tanstack/react-query and @tanstack/react-query-devtools were bumped from 5.81.5 to 5.83.0 in apps/spectator and packages/api, ensuring the latest features and fixes for data management.
• Animation and Utility Libraries: Animation libraries framer-motion (in apps/manager) and motion (in apps/spectator and packages/ui) were updated to 12.23.9. The axios HTTP client was also updated from 1.10.0 to 1.11.0 in apps/spectator and packages/api.
• Development Tooling and Types: Key development dependencies received updates, including turbo (from 2.5.4 to 2.5.5), rollup (from 4.44.2 to 4.45.1), and various ESLint and TypeScript ESLint packages (e.g., @typescript-eslint/eslint-plugin, eslint) to their latest minor/patch versions. The @types/node package was also consistently updated to 22.16.5 across multiple package.json files.
• Package Manager Version: The root package.json now specifies [email protected] as the preferred package manager, updated from [email protected].

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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 updates various package dependencies across the monorepo to their latest minor or patch versions. The updates are consistent across workspaces and align with the PR's goal.

I've found an opportunity to simplify dependencies in tooling/eslint-config/package.json by removing redundant @typescript-eslint packages. This is a good chance to clean up the dependencies while updating them.

Other than that, the changes look solid and are a good maintenance step for the project.

[igbinni143]

수고하셨습니다!