tar bump

[robinroy03]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @robinroy03, 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 primarily focuses on maintaining and updating the project's dependencies. It introduces a new override for @typescript-eslint/utils to standardize its version and bumps several other key package versions to ensure compatibility and leverage the latest features or fixes. Additionally, it performs a significant cleanup of the pnpm-lock.yaml file by removing obsolete dependency entries, which helps in reducing build times and potential conflicts.

Highlights

• Dependency Overrides: Added @typescript-eslint/utils version ^8.38.0 to the package.json overrides to ensure a specific version is used across the project.
• Package Version Bumps: Updated several package specifiers in pnpm-lock.yaml, including @react-router/node, better-auth, react-router, kysely, and set-cookie-parser to newer versions.
• Dependency Cleanup: Removed numerous outdated or unused dependency entries from pnpm-lock.yaml, specifically older versions of @typescript-eslint related packages and other utility libraries, streamlining the dependency tree.

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

[gemini-code-assist]

Code Review

This pull request updates dependencies, most notably upgrading @typescript-eslint packages from v5 to v8 due to a new override. This is a major version bump that introduces breaking changes. I've identified a specific issue in your ESLint configuration that will cause the linting process to fail. Please see my comment on package.json for details. I also recommend updating the pull request title to be more descriptive of these significant changes, as the current title "tar bump" is misleading.

[gemini-code-assist]

Adding this override for @typescript-eslint/utils upgrades all @typescript-eslint packages from v5 to v8. This is a major upgrade with breaking changes that will cause your linting step to fail.

Here are some issues I've identified in your eslint.config.js based on the @typescript-eslint migration guides:

• The rule '@typescript-eslint/explicit-module-boundary-types' (line 38) was removed in v6 of @typescript-eslint/eslint-plugin. It is replaced by '@typescript-eslint/explicit-function-return-type'.
• The rule '@typescript-eslint/no-unused-vars' (line 40) was deprecated in v8. You should remove this line and rely on the base ESLint 'no-unused-vars' rule.

Please review the migration guides for @typescript-eslint v6, v7, and v8 to update your ESLint configuration accordingly.

Given the significance of this change, I also recommend updating the PR title to be more descriptive, for example: chore(deps): bump @typescript-eslint to v8.