fix: update github workflows and urls to use rstackjs organization

[chenjiahan]

Update all references from rspack-contrib to rstackjs in CI workflows, package.json files, and documentation.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[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 migrates all project references from the rspack-contrib organization to the new rstackjs organization. This ensures that documentation links and package metadata correctly point to the updated repository and project homepages, aligning the project's public presence with its new organizational structure.

Highlights

• Documentation Links Updated: All external links within README.md pointing to rspack-contrib.github.io and github.com/rspack-contrib have been updated to rstackjs.github.io and github.com/rstackjs respectively.
• Package Metadata Migration: The homepage, bugs.url, and repository.url fields in both package.json files (package.json and crates/binding/package.json) were updated to reflect the new rstackjs GitHub organization.

🧠 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
  • Updated custom binding guide URL
  • Updated rationale document URL
  • Updated rspack-toolchain repository URL
  • Updated rspack-toolchain supported targets list URL
• crates/binding/package.json
  • Updated homepage URL
  • Updated bugs.url URL
  • Updated repository.url URL
• package.json
  • Updated homepage URL
  • Updated bugs.url URL
  • Updated repository.url URL

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/ci.yml
  • .github/workflows/release.yml
  • .github/workflows/test.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. ↩

[Copilot]

Pull request overview

Updates repository and documentation references to reflect the move from the rspack-contrib organization to rstackjs, ensuring CI workflows and published package metadata point to the correct locations.

Changes:

• Update homepage, bugs.url, and repository.url fields in package manifests to github.com/rstackjs/....
• Update documentation links in README.md to rstackjs.github.io and github.com/rstackjs/....
• Update GitHub Actions workflow uses: references to rstackjs/rspack-toolchain@v1.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
package.json	Updates package metadata URLs to the rstackjs org.
crates/binding/package.json	Updates binding package metadata URLs to the rstackjs org.
README.md	Updates documentation and toolchain links to rstackjs locations.
.github/workflows/test.yml	Switches toolchain action references to rstackjs/rspack-toolchain.
.github/workflows/release.yml	Switches reusable workflow and actions to rstackjs/rspack-toolchain.
.github/workflows/ci.yml	Switches reusable build workflow reference to rstackjs/rspack-toolchain.

---

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

[gemini-code-assist]

Code Review

This pull request updates references from rspack-contrib to rstackjs across documentation and package configuration files. The changes are consistent and correctly applied in README.md, crates/binding/package.json, and the root package.json, reflecting the organization name change in all relevant URLs. The changes are straightforward and I have no suggestions for improvement.

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