chore: dependency bumps via repotools.js#4417
Conversation
Made-with: Cursor
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 40370c312b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@module-federation/enhanced": "0.23.0", | ||
| "@rspack/cli": "1.7.4", | ||
| "@rspack/core": "1.7.4", | ||
| "@module-federation/enhanced": "2.0.1", |
There was a problem hiding this comment.
Regenerate workspace lockfile for bumped dependencies
This dependency bump changes specifiers in workspace packages but the commit does not update pnpm-lock.yaml; for example this package now requests @module-federation/enhanced: 2.0.1, while the lockfile importer for advanced-api/automatic-vendor-sharing/app1 still records specifier: 0.23.0 and @rspack/*: 1.7.4 (pnpm-lock.yaml lines 106-113 in this commit). I checked the CI workflows (.github/workflows/on-push.yml line 91 and .github/workflows/on-pull-request.yml lines 132/219), and they run pnpm install --frozen-lockfile, so these mismatches will make dependency installation fail until the lockfile is regenerated.
Useful? React with 👍 / 👎.
…-lockfile) Made-with: Cursor
…epo e2e) Made-with: Cursor
Dependency bumps across the repo from running
node repotools.js.Includes updates to @rspack, @rsbuild, and other configured packages per repotools.js config.
Made with Cursor