If the version is missing, ask for it before making changes.
-
Check the worktree with git status --short. If there are uncommitted edits, stop and ask the user how to proceed.
-
Run pnpm update @rspack/core@<version> --recursive to update the dependency across all packages in the workspace.
-
Run pnpm i at the repository root.
-
Run pnpm test and pnpm e2e. If either command fails, stop, report the failure, and do not commit or create a PR.
-
Review the diff and confirm it only contains the intended dependency upgrade and lockfile changes. If @rspack/core is already at the target version and there is no diff, report that nothing changed and stop.
-
Commit with this exact message: feat(deps): update @rspack/core to <version>
-
Before pushing, confirm the current branch with git branch --show-current. If it is the default branch, create and switch to a dedicated branch first. Never push the default branch directly.
-
If .github/PULL_REQUEST_TEMPLATE.md exists, keep its structure exactly.
Create the PR with:
- Title:
feat(deps): update @rspack/core to <version>
Summary: Update @rspack/core to <version>.Related Links: https://github.com/web-infra-dev/rspack/releases/tag/v<version>
