Update 1.2 to 1.2.2

[Doezer]

Deps & security fixes
Update to 1.2.2 on dev, tag release then merge into release branch

[gemini-code-assist]

Summary of Changes

Hello @Doezer, 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 systematically updates a wide array of project dependencies to their latest versions. The primary goal is to incorporate recent features, performance enhancements, and critical security fixes across the application's core libraries, development tools, and underlying native modules, ensuring the project remains robust and up-to-date.

Highlights

• Project Version Update: The project's internal version has been updated from 1.2.0 to 1.2.1 in the lockfile.
• Core Dependency Upgrades: Key dependencies such as @tanstack/react-query, dotenv, pino, and react-hook-form have been updated to their latest patch or minor versions.
• ESLint and TypeScript ESLint Updates: All ESLint and TypeScript ESLint related packages have been upgraded, including adjustments to peer dependency ranges to support newer ESLint versions.
• Tailwind CSS Ecosystem Updates: Tailwind CSS related packages (@tailwindcss/vite, @tailwindcss/node, @tailwindcss/oxide) and their native binaries have been updated, with some requiring a minimum Node.js version of 20.

Changelog

• package-lock.json
  • Updated project version from 1.2.0 to 1.2.1.
  • Updated @tanstack/react-query from 5.90.20 to 5.90.21.
  • Updated dotenv from 17.2.4 to 17.3.1.
  • Updated pino from 10.3.0 to 10.3.1.
  • Updated react-hook-form from 7.71.1 to 7.71.2.
  • Updated @eslint/js from 9.39.2 to 9.39.3.
  • Updated @tailwindcss/vite from 4.1.18 to 4.2.0.
  • Updated eslint from 9.39.2 to 9.39.3.
  • Updated typescript-eslint from 8.54.0 to 8.56.0.
  • Updated @tailwindcss/node and @tailwindcss/oxide to 4.2.0, including their platform-specific binaries and adjusting their Node.js engine requirement to >= 20.
  • Updated various @emnapi and @napi-rs related dependencies within @tailwindcss/oxide-wasm32-wasi.
  • Updated enhanced-resolve from 5.18.4 to 5.19.0.
  • Updated lightningcss and its platform-specific binaries from 1.30.2 to 1.31.1.
  • Updated all @typescript-eslint/* packages from 8.54.0 to 8.56.0, and expanded the eslint peer dependency range to include ^10.0.0.
  • Updated minimatch and brace-expansion within @typescript-eslint/typescript-estree.
  • Updated eslint-visitor-keys within @typescript-eslint/visitor-keys.
• package.json
  • Updated @tanstack/react-query from 5.90.20 to 5.90.21.
  • Updated dotenv from 17.2.4 to 17.3.1.
  • Updated pino from 10.3.0 to 10.3.1.
  • Updated react-hook-form from 7.71.1 to 7.71.2.
  • Updated @eslint/js from 9.39.2 to 9.39.3.
  • Updated @tailwindcss/vite from 4.1.18 to 4.2.0.
  • Updated eslint from 9.39.2 to 9.39.3.
  • Updated typescript-eslint from 8.54.0 to 8.56.0.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/ci.yml
  • .github/workflows/deploy.yml

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 several dependencies, which is great for keeping the project up-to-date with the latest features and security fixes. The changes look good overall.

I've added one comment regarding a significant change in the required Node.js version for some development dependencies. The update to @tailwindcss/vite and typescript-eslint now requires Node.js v20+, which could break builds on older environments. I've suggested adding an engines field to package.json to enforce this requirement and ensure a consistent development environment.

Also, I noticed a small discrepancy: the PR title mentions updating to version 1.2.2, but the version in package.json and package-lock.json is updated to 1.2.1. You might want to align these.

[gemini-code-assist]

Code Review

This pull request updates several dependencies, including @tanstack/react-query, dotenv, pino, react-hook-form, @eslint/js, @tailwindcss/vite, eslint, and typescript-eslint. These updates primarily consist of patch and minor version bumps, which align with the pull request's description of 'Deps & security fixes'. A notable change is the increased minimum Node.js version requirement for some transitive dependencies, such as @tailwindcss/oxide and vitest, which now explicitly require Node.js >=20. It is important to ensure the project's engines.node field in package.json is updated to reflect this new minimum requirement for better compatibility and clarity.