chore: upgrade dependencies to latest stable go & js

[gnPy]

Summary by CodeRabbit

• Chores
  • Updated several frontend, documentation, Kubernetes, and TypeScript dependencies.
  • Refreshed build, testing, and linting tool versions across the project.
  • Aligned TypeScript configuration with the latest compiler settings.

[coderabbitai]

Walkthrough

This PR bumps dependency versions across docs, frontend, kubernetes operator, and TypeScript SDK packages. It updates lucide-react, baseline-browser-mapping, radix-ui, ag-grid (major), tanstack/react-query, motion, react-hook-form, tooling devDependencies, k8s.io modules, and TypeScript SDK devDependencies plus tsconfig lib/types settings.

Changes

Dependency version updates across services

Layer / File(s)	Summary
Docs package dependency bumps docs/package.json	Bumps lucide-react and baseline-browser-mapping versions.
Frontend dependency version bumps frontend/package.json	Bumps radix-ui, tanstack/react-query, ag-grid (major v36), lucide-react, motion, react-hook-form, and devDependencies (biome, playwright, types/node, autoprefixer, knip, lint-staged, postcss).
Kubernetes operator module bumps kubernetes/operator/go.mod	Bumps k8s.io/api, apimachinery, client-go, code-generator to v0.36.2 and updates/relocates k8s.io/utils pseudo-version.
TypeScript SDK toolchain updates sdks/typescript/package.json, sdks/typescript/tsconfig.json	Bumps types/node, tsup, typescript, vitest devDependencies and updates tsconfig lib/types/ignoreDeprecations settings.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested labels: refactor

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the dependency upgrades across Go and JavaScript packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

frontend/package.json (1)

38-39: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Migrate the remaining AG Grid v36 selection props in frontend/app/knowledge/page.tsx. suppressRowClickSelection and rowMultiSelectWithClick are deprecated; switch to the rowSelection object API to stay aligned with v36.

🤖 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 AG Grid selection setup in
knowledge page still uses deprecated v36 props, so update the selection
configuration in the knowledge page component to the new rowSelection object
API. Locate the AG Grid usage in knowledge/page.tsx and replace
suppressRowClickSelection and rowMultiSelectWithClick with the equivalent
rowSelection settings, keeping the existing selection behavior unchanged and
aligned with AG Grid v36.

🤖 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.

Nitpick comments:
In `@frontend/package.json`:
- Around line 38-39: The AG Grid selection setup in knowledge page still uses
deprecated v36 props, so update the selection configuration in the knowledge
page component to the new rowSelection object API. Locate the AG Grid usage in
knowledge/page.tsx and replace suppressRowClickSelection and
rowMultiSelectWithClick with the equivalent rowSelection settings, keeping the
existing selection behavior unchanged and aligned with AG Grid v36.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cf8169a0-fed5-424c-90d2-7c1bc3e7a5cd

📥 Commits

Reviewing files that changed from the base of the PR and between 77bd3d6 and f6510a2.

⛔ Files ignored due to path filters (4)

• docs/package-lock.json is excluded by !**/package-lock.json
• frontend/package-lock.json is excluded by !**/package-lock.json
• kubernetes/operator/go.sum is excluded by !**/*.sum
• sdks/typescript/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (8)

• docs/package.json
• frontend/app/globals.css
• frontend/package.json
• frontend/postcss.config.mjs
• frontend/tailwind.config.ts
• kubernetes/operator/go.mod
• sdks/typescript/package.json
• sdks/typescript/tsconfig.json

[coderabbitai]

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`:
- Line 79: The frontend is still configured for Tailwind v3 via the current
tailwindcss dependency and v3 PostCSS/plugin setup, so make an explicit choice:
either document that the project is intentionally staying on v3, or migrate the
frontend to Tailwind v4 by updating the package dependencies and the related
PostCSS and CSS configuration used by the existing frontend setup.

🪄 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: 267fc19a-43ae-4996-a6b7-00612aa1df2d

📥 Commits

Reviewing files that changed from the base of the PR and between f6510a2 and 0e8571c.

⛔ Files ignored due to path filters (1)

• frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• frontend/package.json

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify latest Tailwind and inspect frontend Tailwind/PostCSS config without executing repo code.
npm view tailwindcss version
fd -i '^(postcss|tailwind)\.config\.(js|mjs|cjs|ts)$' frontend --exec sh -c 'echo "---- $1"; sed -n "1,200p" "$1"' sh {}

Repository: langflow-ai/openrag

Length of output: 6723

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== frontend/package.json (Tailwind/PostCSS related deps) =="
python3 - <<'PY'
from pathlib import Path
import json
p = Path("frontend/package.json")
data = json.loads(p.read_text())
for section in ("dependencies", "devDependencies", "peerDependencies"):
    deps = data.get(section, {})
    hits = {k:v for k,v in deps.items() if "tailwind" in k.lower() or "postcss" in k.lower() or "autoprefixer" in k.lower()}
    if hits:
        print(f"[{section}]")
        for k,v in hits.items():
            print(f"{k}: {v}")
PY

echo
echo "== frontend/postcss.config.mjs =="
sed -n '1,120p' frontend/postcss.config.mjs

echo
echo "== frontend/tailwind.config.ts top =="
sed -n '1,80p' frontend/tailwind.config.ts

Repository: langflow-ai/openrag

Length of output: 2605

---

Tailwind v3 vs v4 needs an explicit decision
tailwindcss is still pinned to ^3.4.19, and the frontend config is using the v3 PostCSS/plugin setup. If the goal is “latest stable,” either document this as an intentional v3 hold or include the v4 migration (@tailwindcss/postcss plus the related config/CSS changes).

🤖 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` at line 79, The frontend is still configured for
Tailwind v3 via the current tailwindcss dependency and v3 PostCSS/plugin setup,
so make an explicit choice: either document that the project is intentionally
staying on v3, or migrate the frontend to Tailwind v4 by updating the package
dependencies and the related PostCSS and CSS configuration used by the existing
frontend setup.

Source: Path instructions