chore: bump next version

[Monkiia]

next version is too old might have security issues.

see attached railway alert

test:

successfully build and deployed

[gemini-code-assist]

Summary of Changes

Hello @Monkiia, 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 critical dependency update for the Next.js framework and its associated SWC compiler binaries. The primary motivation is to mitigate potential security risks identified in the older version, ensuring the application leverages the latest stability and security patches. The changes are confined to dependency manifest files, and the author has verified successful build and deployment post-update.

Highlights

• Next.js Version Update: The core Next.js dependency has been updated from version "15.3.1" to "^15.3.8" to address potential security vulnerabilities, as highlighted by a Railway alert.
• SWC Binaries Update: Various @next/swc-* optional dependencies, which are platform-specific SWC compiler binaries, have been updated from version "15.3.1" to "15.3.5" to align with the Next.js update.

🧠 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 the next package from version 15.3.1 to ^15.3.8 to address potential security issues, which is a good and necessary change.

My review includes a comment on the versioning strategy in package.json.

Additionally, I noticed that eslint-config-next in your devDependencies is still at version 15.3.1. It is highly recommended to keep eslint-config-next in sync with the next package version to avoid potential linting inconsistencies. Please consider updating it to ^15.3.8 as well in this PR.

[gemini-code-assist]

The version for the next package has been updated from a pinned version (15.3.1) to a caret-ranged version (^15.3.8). While using a caret range is common for receiving non-breaking updates, it can introduce variability between builds. If your project's policy is to pin dependency versions for maximum reproducibility, you should consider pinning this version as well. Please confirm if this change in versioning strategy is intentional.

Suggested change

	"next": "^15.3.8",
	"next": "15.3.8",