chore: version packages

[ScriptedAlchemy]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @ScriptedAlchemy, 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 is an automated chore to version packages. It specifically updates the rsbuild-plugin-react-router package to version 0.1.1, incorporating two recent patch changes. These changes include enabling Rspack HMR for ESM server outputs and refining the dependency for the dev server's fetch implementation.

Highlights

• Version Update: The rsbuild-plugin-react-router package has been updated to version 0.1.1.
• Rspack HMR for SSR: Enabled Rspack HMR for ESM server outputs by removing the forced dev.hmr=false setting in the React Router plugin.
• Node Fetch Server Dependency: Switched to @remix-run/node-fetch-server for the built-in dev server middleware, reducing direct reliance on @mjackson/node-fetch-server.

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

Changelog

• .changeset/rspack-hmr-for-ssr-dev.md
  • Removed as part of the versioning process, its content has been integrated into the CHANGELOG.md.
• .changeset/use-remix-node-fetch-server.md
  • Removed as part of the versioning process, its content has been integrated into the CHANGELOG.md.
• CHANGELOG.md
  • Added new entries for version 0.1.1 under rsbuild-plugin-react-router, detailing the enablement of Rspack HMR for ESM server outputs and the switch to @remix-run/node-fetch-server.
• package.json
  • Updated the version field from 0.1.0 to 0.1.1 for the rsbuild-plugin-react-router package.

Activity

• This pull request is an automated versioning chore, indicating a release process has been triggered.

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 correctly versions the package to 0.1.1 by updating CHANGELOG.md and package.json. While the versioning changes themselves appear to be an automated commit with no issues, a high-severity Cross-Site Scripting (XSS) vulnerability was identified in the prerendering logic. This vulnerability arises because the plugin generates a static HTML page with unescaped redirect target URLs and current paths during build-time prerendering, which could lead to malicious script injection. It is recommended to implement HTML escaping for all dynamic values inserted into generated HTML templates.