fix: upgrade packages to stable versions#1810
Open
gnPy wants to merge 2 commits into
Open
Conversation
github-actions
Bot
added
community
documentation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (20)
✅ Files skipped from review due to trivial changes (12)
🚧 Files skipped from review as they are similar to previous changes (6)
WalkthroughThis PR updates dependency versions across docs, frontend, and the Kubernetes operator; reorders named exports in many frontend UI modules without changing exported symbols; and makes small frontend code cleanups (truthiness checks and a blank-line insertion). ChangesDependency and Platform Updates
UI Component Module Export Reorganization
Code Cleanup and Formatting
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
github-actions
Bot
added
bug
gnPy
force-pushed
the
fix_upgradeLibraryPy
branch
from
2fffbd0 to
3d3716a
Compare
github-actions
Bot
added
documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
sdks/typescript/package.json (1)
50-53: Confirm dev dependency versions exist; keep a Vitest 4 compatibility check
- Published versions exist for
@types/node@25.9.2,typescript@5.7.3,vitest@4.1.8, andtsup@8.5.1.- Remaining risk is the Vitest major upgrade: ensure
sdks/typescript/vitest.config.ts(and any test setup) is compatible with Vitest 4.x.🤖 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 `@sdks/typescript/package.json` around lines 50 - 53, Verify that the pinned devDependency versions in package.json (`@types/node` 25.9.2, tsup 8.5.1, typescript 5.7.3, vitest 4.1.8) are valid upstream (npm) and, importantly, ensure test config and setup are compatible with Vitest v4 by opening sdks/typescript/vitest.config.ts and any test setup files (e.g., test setup or global-setup hooks) and updating deprecated APIs/option names to the Vitest 4.x equivalents; run the test suite locally with vitest@4.1.8 to confirm no runtime config errors and adjust configuration symbols (vite config export, defineGlobals, setupFiles, reporters, etc.) in vitest.config.ts as needed.
🤖 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 `@kubernetes/operator/go.mod`:
- Around line 7-12: You updated k8s dependencies in go.mod to k8s.io/* v0.36.1
and sigs.k8s.io/controller-runtime v0.24.1; verify compatibility by building and
running tests for the operator and ensure controller-runtime APIs used
(Reconcile, log.FromContext,
ctrl.NewControllerManagedBy(...).For(...).Owns(...).Complete, and client methods
Client.Get/Create/Update and Client.Status().Update) still compile and behave as
expected; if any signature or import issues appear, either align
controller-runtime and k8s.io/* versions to the officially supported pair
(controller-runtime v0.24.x with client-go v0.36.0) or adjust imports/usages to
match the updated patch-level APIs, then commit the go.mod update and
vendor/lock changes after the successful local build/tests.
---
Nitpick comments:
In `@sdks/typescript/package.json`:
- Around line 50-53: Verify that the pinned devDependency versions in
package.json (`@types/node` 25.9.2, tsup 8.5.1, typescript 5.7.3, vitest 4.1.8)
are valid upstream (npm) and, importantly, ensure test config and setup are
compatible with Vitest v4 by opening sdks/typescript/vitest.config.ts and any
test setup files (e.g., test setup or global-setup hooks) and updating
deprecated APIs/option names to the Vitest 4.x equivalents; run the test suite
locally with vitest@4.1.8 to confirm no runtime config errors and adjust
configuration symbols (vite config export, defineGlobals, setupFiles, reporters,
etc.) in vitest.config.ts as needed.
🪄 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: 5a9b7200-3335-46b5-806b-2bd03235c50c
⛔ 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 (20)
docs/package.jsonfrontend/app/api/queries/useGetSearchQuery.tsfrontend/app/onboarding/_components/onboarding-card.tsxfrontend/app/onboarding/_components/onboarding-content.tsxfrontend/components/ui/accordion.tsxfrontend/components/ui/alert.tsxfrontend/components/ui/avatar.tsxfrontend/components/ui/collapsible.tsxfrontend/components/ui/command.tsxfrontend/components/ui/dialog.tsxfrontend/components/ui/dropdown-menu.tsxfrontend/components/ui/popover.tsxfrontend/components/ui/select.tsxfrontend/components/ui/settings-tabs.tsxfrontend/components/ui/sheet.tsxfrontend/components/ui/tabs.tsxfrontend/components/ui/tooltip.tsxfrontend/package.jsonkubernetes/operator/go.modsdks/typescript/package.json
github-actions
Bot
added
bug
lucaseduoli
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
Chores
Style