Conversation
f7e02a1 to
488b831
Compare
2817ee5 to
ace0bb8
Compare
72a8b7b to
7287f9f
Compare
7287f9f to
9442348
Compare
ca46c1a to
cb37206
Compare
98f65de to
99f63a9
Compare
99f63a9 to
c85405a
Compare
6c1077a to
f16eb02
Compare
b472cd0 to
9ec0d54
Compare
9ec0d54 to
360e014
Compare
4446569 to
1e9514a
Compare
7581dae to
f9d41ba
Compare
f9d41ba to
5995cfe
Compare
4a4528b to
6660958
Compare
83eba99 to
4361f93
Compare
4361f93 to
73a7878
Compare
|
You have run out of free Bugbot PR reviews for this billing cycle. This will reset on October 30. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
packages/snage/Dockerfile
Outdated
| @@ -1,4 +1,4 @@ | |||
| FROM node:22.15.0-alpine | |||
| FROM node:25.1.0-alpine | |||
There was a problem hiding this comment.
Bug: Node.js Version Mismatch: Build vs. Runtime
Node.js version mismatch between build environment and runtime. GitHub Actions builds with Node.js 24.11.0 but the Docker container runs with 25.1.0-alpine. This major version difference could introduce runtime incompatibilities or unexpected behavior in production.
packages/snage/package.json
Outdated
| "jest": "30.2.0", | ||
| "jest-junit": "16.0.0", | ||
| "lerna": "8.2.2", | ||
| "lerna": "9.0.3", |
There was a problem hiding this comment.
Bug: ts-jest version incompatible with Jest 30 upgrade
The jest package was upgraded from 29.7.0 to 30.2.0 and @types/jest was correctly updated to 30.0.0, but ts-jest remains at version 29.3.2. The ts-jest library requires major version alignment with jest—ts-jest 29.x only works with jest 29.x. This version mismatch will cause test failures or compatibility issues since the project uses ts-jest as its preset in jest.config.js.
Additional Locations (1)
| "react": "19.1.0", | ||
| "react-dom": "19.1.0", | ||
| "react-markdown": "9.1.0", | ||
| "react-markdown": "10.1.0", |
There was a problem hiding this comment.
Bug: Removed className prop used with react-markdown v10
The upgrade from react-markdown 9.1.0 to 10.1.0 introduces a breaking change: the className prop was removed in v10.0.0. However, the code in packages/ui/src/ReactMarkdown.tsx at line 40 still passes className={classes.root + ' markdown-body'} to the <Markdown> component. This prop will now be silently ignored, causing the markdown content to render without the intended styling. The migration requires wrapping the component in an element with the desired class instead.
| "winston": "3.17.0", | ||
| "yaml": "2.7.1", | ||
| "yargs": "17.7.2" | ||
| "yargs": "18.0.0" |
There was a problem hiding this comment.
Bug: Yargs 18 ESM-only breaks CommonJS require calls
The update to yargs 18.0.0 will break the application at runtime. Yargs 18 is ESM-only and cannot be imported using CommonJS require(). The docs.js file uses const yargs = require('yargs'), and the TypeScript source is configured to compile to CommonJS ("module": "commonjs" in tsconfig). When the code attempts to load yargs, it will fail because ESM-only packages cannot be loaded with require() in a CommonJS context.
packages/snage/package.json
Outdated
| "env-editor": "0.5.0", | ||
| "get-port": "7.1.0", | ||
| "jest": "29.7.0", | ||
| "jest": "30.2.0", |
There was a problem hiding this comment.
ts-jest 29 incompatible with jest 30 major upgrade
High Severity
jest is updated from 29.7.0 to 30.2.0, but ts-jest remains at 29.3.2. ts-jest must match the major version of jest — version 29.x only supports jest 29.x. Additionally, the jest.config.js uses the globals config key to pass ts-jest settings (isolatedModules), which was removed in Jest 30. This will completely break the test suite.
Additional Locations (1)
| "winston": "3.17.0", | ||
| "yaml": "2.7.1", | ||
| "yargs": "17.7.2" | ||
| "yargs": "18.0.0" |
There was a problem hiding this comment.
yargs 18 removes .argv and CJS require() support
High Severity
Upgrading yargs from 17 to 18 introduces two breaking changes that aren't addressed. First, yargs 18 removes the .argv property (singleton pattern), but both docs.js line 32 and packages/snage/src/index.ts line 35 rely on .argv to trigger argument parsing — these need to use .parse() instead. Second, yargs 18 is ESM-only, but docs.js uses require('yargs') which will fail. The application's main entry point and docs script will both break at runtime.
| "winston": "3.17.0", | ||
| "yaml": "2.7.1", | ||
| "yargs": "17.7.2" | ||
| "yargs": "18.0.0" |
There was a problem hiding this comment.
Yargs 18 removes singleton API used throughout codebase
High Severity
yargs is bumped from 17 to 18, which removes the singleton pattern. The code in index.ts calls yargs.version(...)...argv directly on the default import — this singleton usage was explicitly removed in yargs 18. Additionally, all command files reference yargs.CommandModule via the namespace, which is also removed in v18. The application will fail to start.
| "react": "19.1.0", | ||
| "react-dom": "19.1.0", | ||
| "react-markdown": "9.1.0", | ||
| "react-markdown": "10.1.0", |
There was a problem hiding this comment.
react-markdown 10 removes className prop and ExtraProps
Medium Severity
react-markdown is bumped from 9 to 10, which removed the className prop and the ExtraProps type export. ReactMarkdown.tsx imports ExtraProps from react-markdown (no longer exported) and passes className to the <Markdown> component (no longer accepted). The UI build will fail, and if somehow bypassed, the markdown styling will be lost.
packages/ui/package.json
Outdated
| "@mui/icons-material": "6.4.11", | ||
| "@mui/material": "6.4.11", | ||
| "@mui/icons-material": "7.3.8", | ||
| "@mui/material": "7.3.8", |
There was a problem hiding this comment.
@mui/styles v6 incompatible with @mui/material v7
Medium Severity
@mui/material is bumped to v7 but @mui/styles remains at v6.4.8. The @mui/styles package (JSS-based) is incompatible with @mui/material v7. The UI uses makeStyles, withStyles, and ThemeProvider from @mui/styles in multiple files, while createTheme comes from @mui/material/styles v7. The theme objects between v6 and v7 may be structurally different, causing styling failures.
packages/ui/package.json
Outdated
| "@mui/icons-material": "6.4.11", | ||
| "@mui/material": "6.4.11", | ||
| "@mui/icons-material": "7.3.8", | ||
| "@mui/material": "7.3.8", |
There was a problem hiding this comment.
MUI v7 removed InputProps from TextField component
High Severity
Upgrading @mui/material from v6 to v7 removes the InputProps prop from TextField. In App.tsx, the search TextField passes InputProps={{ endAdornment: ... }} containing the close, help, and export IconButton components. In MUI v7, this prop is silently ignored, causing all search bar action buttons to disappear. The migration path is to use slotProps={{ input: { endAdornment: ... } }} instead.
| "winston": "3.17.0", | ||
| "yaml": "2.7.1", | ||
| "yargs": "17.7.2" | ||
| "yargs": "18.0.0" |
There was a problem hiding this comment.
yargs 18 ESM-only breaks CommonJS test execution
High Severity
yargs is updated to 18.0.0, which is ESM-only, but the project's tsconfig.json uses "module": "commonjs". When ts-jest or ts-node compiles TypeScript, import yargs from 'yargs' becomes require('yargs'), which fails for ESM-only packages. This will break test execution and the ts-node dev command for any code path that transitively imports yargs. The webpack production build may still work since webpack handles ESM natively.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| "winston": "3.17.0", | ||
| "yaml": "2.7.1", | ||
| "yargs": "17.7.2" | ||
| "yargs": "18.0.0" |
There was a problem hiding this comment.
Yargs 18 removed .argv and singleton usage
High Severity
Upgrading yargs to 18.0.0 will break the CLI entirely. Yargs 18 removed singleton .argv usage, which index.ts relies on (yargs.version(...)...argv). Additionally, yargs 18 is ESM-first while the project uses CommonJS ("module": "commonjs"), and the yargs.CommandModule namespace type used across all command files may no longer be available.


This PR contains the following updates:
6.4.11→7.3.96.4.11→7.3.929.5.14→30.0.022.15.3→25.5.022.15.3→25.5.06.0.3→7.2.0v4→v5v4→v6v4→v8v4→v6v4→v77.0.3→10.1.028.11.0→29.15.05.2.0→7.0.156.0.1→63.0.04.21.2→5.2.129.7.0→30.3.08.2.2→9.0.722.15.0→24.14.022.15.0-alpine→25.8.1-alpine9.1.0→10.1.015.6.1→16.1.16.0.1→7.0.117.7.2→18.0.0Release Notes
mui/material-ui (@mui/icons-material)
v7.3.9Compare Source
A big thanks to the 15 contributors who made this release possible.
@mui/material@7.3.9color-mixvalue on top of default generated Material UI CSS variables (#47791) @ZeeshanTambolialphabefore color mixing to border bottom color when nativeColor + cssVariables is used (#47840) @ZeeshanTamboliDocs
(0, 1]behavior. (#47851) @matthias-ccrinativeColordocs (#47759) (#47789) @ZeeshanTamboliCore
All contributors of this release in alphabetical order: @alelthomas, @arthur-plazanet, @brijeshb42, @DanailH, @dav-is, @Janpot, @matthias-ccri, @mnajdova, @oliviertassinari, @pavan-sh, @PeterTYLiu, @sai6855, @silviuaavram, @vmakhaev, @ZeeshanTamboli
v7.3.8Compare Source
Feb 12, 2026
A big thanks to the 15 contributors who made this release possible. Here are some highlights ✨:
@mui/material@7.3.8disableCloseOnSelect(#47248) @ZeeshanTambolionDeletecheck (#47753) @ZeeshanTamboliaria-disabledfrom root span (#46318) @KirankumarAmbatipersistentandpermanentvariant Drawers should not override the styles via theme usingmodalclass (#47581) @ZeeshanTamboliReact.Keyinstead ofanyforkeyprop (#47619) @sonixx02Core
868d23e) @dav-isae29d03) @dav-iswindow.muiDocConfig(#47737) @JanpotDocs
All contributors of this release in alphabetical order: @aditya1906, @aemartos, @alelthomas, @bernardobelchior, @dav-is, @Janpot, @KirankumarAmbati, @mapache-salvaje, @nodirbekprogrammer, @Ocheretovich, @oliviertassinari, @sai6855, @silviuaavram, @sonixx02, @ZeeshanTamboli
v7.3.7Compare Source
Jan 8, 2026
A big thanks to the 16 contributors who made this release possible.
@mui/material@7.3.7squareprop on Accordion Root (#47457) @ZeeshanTamboliArrowLeft,Backspace&Deletebehavior for multiple and single-value rendering with proper caret handling (#47411) @jnbainclassesfrom root slot (#47519) @ZeeshanTambolicontained(#47499) @ZeeshanTamboliactiveElementinsideloopFocuson every keydown (#47566) @ZeeshanTamboliDocs
Core
@mui/internal-test-utilsto code infra repo (#47422) @JanpotAll contributors of this release in alphabetical order: @AarishMansur, @alelthomas, @atharva3333, @bricefrisco, @Janpot, @jnbain, @joserodolfofreitas, @mapache-salvaje, @mj12albert, @oliviertassinari, @prakhargupta1, @rithik56, @siriwatknp, @TimKraemer, @Zache, @ZeeshanTamboli
v7.3.6Compare Source
Dec 3, 2025
A big thanks to the 22 contributors who made this release possible.
@mui/material@7.3.6
filterSelectedOptionsdependency fromsyncHighlightedIndexuseCallback (#47378) @ZeeshanTambolisecondaryActionslot toListItem(#47399) @sai6855marksprop (#47370) @pcorpetownerStatespread intouseSnackbar(#47373) @ZeeshanTamboliapplyStyleswith custom color schemes (#47242) @akankshahu@mui/system@7.3.6
classattribute (#47200) @siriwatknp@mui/lab@7.3.6
Docs
elevationandsquareprops (#47261) @Ad1tya-007Core
next/fontfor local fonts (#47351) @Janpotappsfolder (#47183) @Janpotnext/font(#47347) @JanpotComponentLinkHeaderbottom margin (#47328) @Janpotnext.config.jstonext.config.mjs(#44040) @albarv340mui-materialpackage (#47392) @ZeeshanTamboliclean-csspackage from docs (#47314) @ZeeshanTambolibuidApiDocs->buildApiDocs(#47235) @Ad1tya-007@vitest/browserand@vitest/coverage-v8(#47189) @ZeeshanTamboliAll contributors of this release in alphabetical order: @Ad1tya-007, @akankshahu, @albarv340, @Aleksan4e3, @brijeshb42, @Copilot, @Fanzzzd, @Janpot, @JCQuintas, @kumarvishwajeettrivedi, @mapache-salvaje, @oliviertassinari, @pcorpet, @rifeplight, @rithik56, @rossdakin, @sai6855, @shamblonaut, @siriwatknp, @vrachuri28, @xBlizZer, @ZeeshanTamboli
v7.3.5Compare Source
Nov 4, 2025
A big thanks to the 11 contributors who made this release possible.
@mui/material@7.3.5theme.vars.shapemodule augmentation (#47164) @siriwatknp@mui/material-nextjs@7.3.5Docs
inputPropswithslotProps.inputin checkbox demos (#47083) @CODEKRUNCHCore
@mui/internal-test-utils(#47141) @bernardobelchiorConfiguration
📅 Schedule: Branch creation - "on the 1 day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.