chore(deps): consolidate Dependabot updates#389
Conversation
|
Warning Review limit reached
Next review available in: 44 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_3b1bb8b5-e7be-4ced-aac5-eb504dabc307) |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bef58abd15
ℹ️ 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".
| "lucide-react": "1.16.0", | ||
| "react": "19.2.6", | ||
| "react-dom": "19.2.6", | ||
| "react-dom": "19.2.7", |
There was a problem hiding this comment.
When the admin dashboard is installed from this manifest, react-dom@19.2.7 is resolved next to react@19.2.6; the updated lockfile records react-dom's peer as react: ^19.2.7, so the direct dependency no longer satisfies the renderer it loads. This leaves the frontend on an unsupported/mismatched React runtime and can surface as peer-resolution failures or React/ReactDOM runtime incompatibilities; bump react to 19.2.7 (or keep both at 19.2.6) and regenerate the lockfile.
Useful? React with 👍 / 👎.
| "dependencies": { | ||
| "@tailwindcss/vite": "4.3.1", | ||
| "@vitejs/plugin-react": "6.0.2", | ||
| "@vitejs/plugin-react": "6.0.3", |
There was a problem hiding this comment.
This dependency bump changes the admin dashboard build/runtime inputs, but the served bundle under apps/api/src/five08/backend/static/dashboard is unchanged; I checked the diff and no static dashboard files were regenerated, while scripts/check-all.sh rebuilds this app and diffs it against the committed static directory. In deployments that serve the committed FastAPI static bundle, users will keep receiving the old dashboard assets, and the full check will fail once dependencies are installed. Rebuild the dashboard and commit the generated static assets with this manifest update.
Useful? React with 👍 / 👎.
|
@dependabot rebase |
bef58ab to
f5f3387
Compare
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_f495aaba-29d6-4696-b78a-2784eeac4fe6) |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f5f338701d
ℹ️ 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".
| "@types/bun": "1.3.14", | ||
| "@types/react": "19.2.14", |
There was a problem hiding this comment.
In the current apps/admin_dashboard/package.json, devDependencies still request @types/react 19.2.15 and do not include @types/bun, but this lockfile snapshot now records @types/bun plus @types/react 19.2.14. Bun uses this workspace block as the package manifest snapshot; I checked bun install --help, and --frozen-lockfile disallows lockfile changes, so installs from this committed lock will try to rewrite/fail instead of being reproducible. Regenerate bun.lock from the committed package.json.
Useful? React with 👍 / 👎.
1 participant
Consolidates the open Dependabot updates in this repository into one reviewable PR.
Included PRs:
This branch applies the dependency manifest and lockfile changes from the listed Dependabot PRs against
main.Note
Medium Risk
TypeScript 6 and dramatiq 2.2 on the job broker are the main regression vectors; otherwise routine dependency maintenance with no runtime code edits.
Overview
Merges multiple open Dependabot PRs into one pass over manifests and lockfiles only—no application source changes.
Admin dashboard (
apps/admin_dashboard): bumps the React/Vite toolchain (react-dom,@vitejs/plugin-react, Vite 8.1, Vitest 4.1.9, Biome), and moves TypeScript from 5.9 to 6.0;bun.lockis regenerated (including Rolldown/Vite transitive updates and@types/bunin the lockfile).Python monorepo: raises
pydantic-settingsfrom ~2.8 to ~2.14 in api, discord_bot, worker, and shared; bumps the worker’s pinneddramatiq[redis]from 2.0.1 to 2.2.0; and refreshes root dev deps (coverage ~7.14, playwright ≥1.60) with a matchinguv.lockrefresh.Reviewed by Cursor Bugbot for commit f5f3387. Bugbot is set up for automated code reviews on this repo. Configure here.