chore: upgrade dependencies to latest stable go & js#1998
Conversation
…v4 migration, typescript v6 fixes, k8s 0.36.2)
github-actions
Bot
added
documentation
WalkthroughThis PR updates dependency versions across multiple project manifests: docs/package.json, frontend/package.json, kubernetes/operator/go.mod, and sdks/typescript/package.json, plus tsconfig.json compiler option changes for the TypeScript SDK. ChangesDependency Updates
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
|
Build successful! ✅ |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@frontend/package.json`:
- Around line 38-39: The knowledge grid selection setup still uses the legacy AG
Grid selection props, so update the grids in knowledge page handling to the v36
object-based API. In the component that renders both AG Grid instances, replace
string rowSelection usage like rowSelection="multiple" with the new selection
config object, and remove or migrate suppressRowClickSelection to the equivalent
v36 selection behavior. Keep the changes localized to the grid configuration so
both grids continue to support multi-select without regressions.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d8bc9f2d-e99c-42ca-b451-fb7dfb602c72
⛔ Files ignored due to path filters (4)
docs/package-lock.jsonis excluded by!**/package-lock.jsonfrontend/package-lock.jsonis excluded by!**/package-lock.jsonkubernetes/operator/go.sumis excluded by!**/*.sumsdks/typescript/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (5)
docs/package.jsonfrontend/package.jsonkubernetes/operator/go.modsdks/typescript/package.jsonsdks/typescript/tsconfig.json
| "ag-grid-community": "^36.0.0", | ||
| "ag-grid-react": "^36.0.0", |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
What are the breaking changes in ag-grid v36.0.0 migration guide for React?
💡 Result:
AG Grid v36.0.0, released on June 24, 2026, introduces new features such as user-defined calculated columns, automatic column generation, and a new show values as capability [1][2]. Official documentation indicates that migration guides for this version are available on the AG Grid website [3][4]. Notably, AG Grid has discontinued the use of Codemods for version 36.0.0 and later, meaning that developers must manually address any breaking, behavioral, or styling changes during the upgrade process [4]. Unlike previous versions that offered automated transformation scripts, there is no Codemod available for this major release [4]. For detailed information regarding specific breaking changes, behavior modifications, and styling updates required for your project, refer to the official 36.0.0 Migration Guide located in the React Grid documentation section of the AG Grid website [3][5]. The release also includes updates to AG Charts (v14.0.0), which may necessitate additional adjustments depending on your chart configuration [5].
Citations:
- 1: https://github.com/ag-grid/ag-grid/releases/tag/release-36.0.0
- 2: https://blog.ag-grid.com/whats-new-in-ag-grid-36/
- 3: https://www.ag-grid.com/react-data-grid/migration/
- 4: https://www.ag-grid.com/javascript-data-grid/migration/
- 5: AG-17593 Add release content for 36.0.0 ag-grid/ag-grid#14153
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Inspect the package and knowledge page usage
printf '\n== package.json ==\n'
cat -n frontend/package.json | sed -n '1,140p'
printf '\n== knowledge page ==\n'
cat -n frontend/app/knowledge/page.tsx | sed -n '1,240p'
printf '\n== ag-grid usages ==\n'
rg -n "AgGridReact|ag-grid|gridOptions|columnDefs|defaultColDef|theme=|themeClass|rowSelection|suppress|domLayout|enableCharts|sideBar|statusBar" frontend -g '!**/node_modules/**'Repository: langflow-ai/openrag
Length of output: 20623
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Map and inspect AG Grid-related files with line numbers
git ls-files 'frontend/**' | rg 'ag-grid|knowledge/page\.tsx|package\.json$'Repository: langflow-ai/openrag
Length of output: 245
🌐 Web query:
AG Grid v36 migration guide breaking changes themeQuartz.withParams browserColorScheme rowSelection suppressRowClickSelection AgGridReact React
💡 Result:
AG Grid v36 was released on June 24, 2026 [1][2]. Unlike previous major versions (v31–v35), there are no automated Codemods available for upgrading to v36 [1][3]. You should consult the official "Upgrading to AG Grid 36" migration guide on the AG Grid website to identify breaking changes, behavioral adjustments, and styling updates specific to your implementation [1][4]. Regarding your specific configuration queries: 1. themeQuartz.withParams and browserColorScheme: The Theming API (introduced in v32.2) allows you to use themeQuartz.withParams() to configure theme parameters [5]. The browserColorScheme parameter is a color scheme value that accepts standard CSS color-scheme values (e.g., 'light', 'dark', 'normal', 'inherit') [6][7]. This is used to define how the grid responds to system or application-level theme preferences [7]. 2. Row Selection Configuration: The property suppressRowClickSelection was deprecated in version 32.2 [8][9]. If you are still using it, you should migrate to the rowSelection object configuration [8][9]. The modern approach is to use rowSelection.enableClickSelection to manage whether clicking a row triggers selection [8][9]. Note that modern rowSelection options also require using an object configuration (e.g., rowSelection = { mode: 'singleRow' | 'multiRow', ... }) rather than the older string-based 'single' or 'multiple' values [9]. For React developers using AgGridReact, ensure your gridOptions or component props reflect these modern configuration structures, as the underlying grid engine enforces these validation rules regardless of the framework [9]. Given the lack of automated codemods for v36, manual review of your grid configurations is recommended [1][3].
Citations:
- 1: https://www.ag-grid.com/javascript-data-grid/migration/
- 2: https://github.com/ag-grid/ag-grid/releases/tag/release-36.0.0
- 3: https://www.ag-grid.com/react-data-grid/migration/
- 4: AG-17593 Add release content for 36.0.0 ag-grid/ag-grid#14153
- 5: https://blog.ag-grid.com/introducing-our-new-theming-api/
- 6: https://www.ag-grid.com/javascript-data-grid/theming-parameters/
- 7: https://www.ag-grid.com/javascript-data-grid/theming-colors/
- 8: https://www.ag-grid.com/javascript-data-grid/upgrading-to-ag-grid-32-2-1/
- 9: https://github.com/ag-grid/ag-grid/blob/e6f9ec1f/packages/ag-grid-community/src/validation/rules/gridOptionsValidations.ts
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Read the two AgGridReact instances and nearby config in frontend/app/knowledge/page.tsx
sed -n '980,1095p' frontend/app/knowledge/page.tsx | cat -nRepository: langflow-ai/openrag
Length of output: 5924
Migrate the knowledge grids to the AG Grid v36 selection API. frontend/app/knowledge/page.tsx still uses the legacy string rowSelection="multiple" in both grids, and one grid also relies on suppressRowClickSelection; switch those to the object-based rowSelection config to avoid selection regressions.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@frontend/package.json` around lines 38 - 39, The knowledge grid selection
setup still uses the legacy AG Grid selection props, so update the grids in
knowledge page handling to the v36 object-based API. In the component that
renders both AG Grid instances, replace string rowSelection usage like
rowSelection="multiple" with the new selection config object, and remove or
migrate suppressRowClickSelection to the equivalent v36 selection behavior. Keep
the changes localized to the grid configuration so both grids continue to
support multi-select without regressions.
edwinjosechittilappilly
left a comment
edwinjosechittilappilly
left a comment
There was a problem hiding this comment.
code LGTM
3 participants
Summary by CodeRabbit