docs: add migration guide from connect to connect-next

[chenjiahan]

Add instructions for migrating from the connect package to the new connect-next package. Include steps for removing old dependencies, installing the new package, and updating imports. Also mention that TypeScript types are now included in the package.

[gemini-code-assist]

Summary of Changes

Hello, 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 introduces a new migration guide to assist users in transitioning their projects from the older connect package to the more modern connect-next. The guide simplifies the upgrade process by detailing dependency changes and import syntax adjustments, ensuring a smoother adoption of the updated package.

Highlights

• Migration Guide: Added a comprehensive guide for migrating existing projects from the connect package to the connect-next package.
• Dependency Management: Provided instructions for removing the legacy connect and @types/connect packages and installing connect-next.
• TypeScript Support: Clarified that connect-next now includes its own TypeScript types, eliminating the need for @types/connect.
• Import Syntax Update: Illustrated the change in import syntax, moving from a default import to a named connect export from connect-next.

🧠 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

• README.md
  • Added a new section for migrating from connect to connect-next.
  • Included steps for dependency removal and installation.
  • Provided guidance on updating import statements and noted built-in TypeScript types.

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 adds a helpful migration guide to the README.md for users moving from connect to connect-next. The instructions are clear and cover dependency changes and import updates. I've suggested one improvement to make the guide more comprehensive by including instructions for other popular package managers like yarn and pnpm.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[Copilot]

Pull request overview

Adds a short migration guide to help users move from the legacy connect package to connect-next, aligning installation and import patterns with the fork’s ESM + bundled-types setup.

Changes:

• Document uninstalling connect and @types/connect, then installing connect-next.
• Call out that connect-next includes its own TypeScript types.
• Document the import change from a default connect import to a named { connect } export.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.