-
Notifications
You must be signed in to change notification settings - Fork 0
chore: update dependencies #172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
MinCrohn
commented
Jan 13, 2026
- Updated @biomejs/biome, @commitlint/cli, and @commitlint/config-conventional to version 2.3.11 and 20.3.1 respectively.
- Upgraded gsap to version 3.14.2.
- Updated @vitest/browser and @vitest/browser-playwright to version 4.0.17.
- Updated pixi.js to version 8.15.0 and playwright to version 1.57.0.
- Updated rollup to version 4.55.1.
- Updated lint-staged to version 16.2.7.
- Removed unused dependencies from package-lock.json.
- Updated @biomejs/biome, @commitlint/cli, and @commitlint/config-conventional to version 2.3.11 and 20.3.1 respectively. - Upgraded gsap to version 3.14.2. - Updated @vitest/browser and @vitest/browser-playwright to version 4.0.17. - Updated pixi.js to version 8.15.0 and playwright to version 1.57.0. - Updated rollup to version 4.55.1. - Updated lint-staged to version 16.2.7. - Removed unused dependencies from package-lock.json.
Summary of ChangesHello @MinCrohn, 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 routine maintenance by updating a comprehensive set of project dependencies. The updates span core libraries, development tools, and testing frameworks, ensuring the project benefits from the latest features, performance improvements, and security patches. This keeps the project aligned with current best practices and reduces technical debt without introducing new features or breaking changes. Highlights
🧠 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 AssistThe 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
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 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
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request updates several dependencies to their latest versions. The changes look good, especially the update to lint-staged v16 which reduces the number of transitive dependencies. I have one suggestion related to the Biome configuration to ensure it stays in sync with the updated package version.