Conversation
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Skipped: No reviewable files found. |
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered development platform that enables users to create web applications by interacting with AI agents in real-time sandboxes. It features a Next.js/React front-end with a rich UI including file explorers, live previews, conversational project development, and integrated authentication and background job processing. The platform relies on a robust backend built with Express, among other technologies, to serve dynamic content and API endpoints. PR ChangesThis pull request bumps express from version 4.21.2 to 4.22.1. The update includes security fixes, dependency adjustments, and minor refactoring for improved error handling and performance. Although primarily a backend dependency change, it may affect how errors are handled and presented in user-facing pages, as well as overall reliability of API responses. Setup Instructions
Generated Test Cases1: Home Page Loads Successfully ❗️❗️❗️Description: Verifies that the main homepage loads correctly after the Express update, ensuring that the upgrade does not disrupt the primary user interface or routing. Prerequisites:
Steps:
Expected Result: The home page should render without errors, displaying the expected design elements, navigation, and content as per the design specifications. 2: Non-Existent Route Displays Custom 404 Error Page ❗️❗️❗️Description: Checks that navigating to a non-existent route triggers a friendly and informative 404 error page, ensuring that error handling continues to work correctly after the Express upgrade. Prerequisites:
Steps:
Expected Result: A custom 404 error page should appear with a clear, user-friendly message explaining that the page cannot be found, and possibly a link back to the home page. 3: API Error Endpoint Renders User-Friendly Error Message ❗️❗️Description: Ensures that when the backend (powered by Express) returns an error (for instance, when an API endpoint is accessed incorrectly), the error message is rendered in a user-friendly manner on the UI. Prerequisites:
Steps:
Expected Result: The user should see a well-formatted, user-friendly error message indicating that something went wrong, rather than a raw stack trace or a confusing server error. The UI error page should align with the overall design of the platform. Raw Changes Analyzed |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
🚀 Scrapybara Ubuntu instance started! |
|
🔧 Setting up test environment... Agent Steps |
|
❌ Something went wrong: |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/express-4.22.1
branch
from
ba72f92 to
3880a05
Compare
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered development platform that enables users to create and manage web applications in real-time sandboxes. The application leverages Next.js, React, and various modern libraries to provide live previews, conversational project development, and advanced file management. PR ChangesThis pull request bumps express from version 4.21.2 to 4.22.1. The update includes a security patch (with a subsequent revert for one of the fixes), improved error handling for method functions with no path, internal refactorings for better code readability, and updated dependency notations. Setup InstructionsInstall pnpm globally if not already installed by running 'sudo npm install -g pnpm'. Then, navigate to your repository directory using the terminal and run 'pnpm install' to install all dependencies. Next, start the development server by running 'pnpm dev'. Once the server is running, open your web browser and navigate to 'http://localhost:3000' to view the application. Generated Test Cases1: Home Page Loads Successfully ❗️❗️❗️Description: Verifies that the application’s home page renders correctly after the Express update. This ensures that routing and page rendering are functioning as expected. Prerequisites:
Steps:
Expected Result: The home page loads cleanly with all expected elements visible and with correct layout, indicating that the Express bump has not disrupted routing or UI rendering. 2: 404 Error Page for Non-existent Routes ❗️❗️Description: Checks that the application correctly handles invalid routes by displaying a custom 404 error page. This is critical to ensure that user navigation mishaps are handled gracefully. Prerequisites:
Steps:
Expected Result: A custom 404 error page appears, informing the user that the page is not found. The page should also provide navigational options or links back to valid parts of the application. 3: API Error Display for Faulty Method Invocation ❗️❗️❗️Description: Ensures that if an API is called in an unexpected manner (for example, a method function with no defined path), the application displays a clear error message. This test validates the improved error handling introduced in the Express update. Prerequisites:
Steps:
Expected Result: The error is caught and a user-friendly error dialog or page is displayed, clearly explaining that an error occurred without exposing sensitive details. 4: Navigation Functionality Remains Intact ❗️❗️Description: Checks that internal navigation between different sections of the application works smoothly without any routing issues after the Express update. Prerequisites:
Steps:
Expected Result: Navigation between pages is seamless, with each page loading correctly and reflecting the intended content. There are no unexpected errors or layout issues. 5: User Sign-In Modal Display ❗️❗️❗️Description: Validates that the user authentication flow is functioning correctly by ensuring that the sign-in modal appears when a non-authenticated user attempts to sign in. This confirms that the Express server update did not interfere with authentication endpoints. Prerequisites:
Steps:
Expected Result: The sign-in modal or authentication page opens promptly, displaying the necessary input fields for credentials. There should be no disruption in the sign-in flow. Raw Changes Analyzed |
|
🚀 Launching Scrapybara desktop... |
|
❌ Something went wrong: |
|
Dependabot doesn't support the 'updating transitive dependencies' feature for pnpm package_manager. Because of this, Dependabot cannot update this pull request. |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/express-4.22.1
branch
from
3880a05 to
24741c3
Compare
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered development platform that allows users to create web applications by interacting with AI agents in real-time sandboxes. The platform features project creation, live previews, conversational development, file exploration, and integrated authentication, among other features. PR ChangesThis pull request bumps Express from version 4.21.2 to 4.22.1. Although the change is primarily a backend dependency update, it can indirectly affect user-facing aspects such as how error pages are rendered and how routes are processed. Additionally, some related dependency versions such as @clerk/nextjs and convex dependencies have been updated, which might impact authentication flows and other UI modules that rely on these libraries. Setup Instructions
Generated Test Cases1: Home Page Loads and Renders Correctly ❗️❗️❗️Description: Verifies that the main homepage loads without errors, renders all critical UI components (navigation, logos, and landing text) as expected, and that there are no visual disruptions after updating Express. Prerequisites: Steps:
Expected Result: The homepage loads without any errors. All UI elements are visible, correctly aligned, and functional. Navigation links and interactive elements work as expected. 2: Invalid Route Displays Correct Error Page ❗️❗️❗️Description: Ensures that navigating to a non-existent URL results in a properly rendered error page. Given the Express update, the error handling behavior should remain consistent and user-friendly. Prerequisites: Steps:
Expected Result: The user should see a clear 404 error page or equivalent error message with appropriate design and navigation options to return to a valid page. 3: User Sign-In Form Error Handling ❗️❗️❗️Description: Checks that the sign-in page correctly handles invalid inputs by displaying error messages, ensuring that updates to dependencies like @clerk/nextjs have not disrupted the authentication UI. Prerequisites:
Steps:
Expected Result: An error message should be visibly displayed, informing the user that the provided credentials are invalid or incomplete. The form should clearly indicate which fields need correction without any layout issues. Raw Changes AnalyzedFile: pnpm-lock.yaml
Changes:
@@ -12,9 +12,12 @@ importers:
.:
dependencies:
+ '@clerk/nextjs':
+ specifier: ^6.35.6
+ version: 6.35.6(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
'@convex-dev/auth':
specifier: ^0.0.90
- version: 0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)
+ version: 0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)
'@databuddy/sdk':
specifier: ^2.2.1
version: 2.3.0(@babel/core@7.28.4)(@babel/template@7.27.2)(@types/react@19.2.7)(react@19.2.1)
@@ -176,7 +179,7 @@ importers:
version: 1.1.1(@types/react-dom@19.2.3(@types/react@19.2.7))(@types/react@19.2.7)(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
convex:
specifier: ^1.29.0
- version: 1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
+ version: 1.30.0(@clerk/clerk-react@5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
csv-parse:
specifier: ^6.1.0
version: 6.1.0
@@ -524,15 +527,27 @@ packages:
'@bufbuild/protobuf@2.9.0':
resolution: {integrity: sha512-rnJenoStJ8nvmt9Gzye8nkYd6V22xUAnu4086ER7h1zJ508vStko4pMvDeQ446ilDTFpV5wnoc5YS7XvMwwMqA==}
- '@clerk/clerk-react@5.51.0':
- resolution: {integrity: sha512-jBreKiUS4DKm+JUIt59B1699aRr3wQmQ1O+DlWCEY3iEz+F6ETir1SJcRNG5mHVoA9EGn+m93USJSUWZBRG8yQ==}
+ '@clerk/backend@2.25.0':
+ resolution: {integrity: sha512-hezdPE8B7iXCWQZRDh5oj9U3xMkLAM/XlbGDwOaWKiNUtTHN9DKTS7c7hx7m2ttHwjAqRZkGZ+7lidEjJWAYFw==}
+ engines: {node: '>=18.17.0'}
+
+ '@clerk/clerk-react@5.57.1':
+ resolution: {integrity: sha512-WpSxJBt9XamN087wj1d8eAs3u20JWdnqUK9vHS5E+tEEd0hgDi3rpNIfsgNVHBAi/rS78DggrAc8db+WOGrJ1Q==}
engines: {node: '>=18.17.0'}
peerDependencies:
react: ^18.0.0 || ^19.0.0 || ^19.0.0-0
react-dom: ^18.0.0 || ^19.0.0 || ^19.0.0-0
- '@clerk/shared@3.27.3':
- resolution: {integrity: sha512-OJqWwlQGi6XMVWJVtY1YmOESAkEAflDrynFSjwQQ/sC8c4hmUukIq07XTOlcv6j4u1i4akhtNwy40B1qiRrLdg==}
+ '@clerk/nextjs@6.35.6':
+ resolution: {integrity: sha512-4/OL1SQw1hprRGCAfNwZ01GmXfsDRi2sr8Y63/hOLuLM5A7wT5Ft1eAPTeVtoWKF8+G3M+n/vbyqYwY8l7VUzg==}
+ engines: {node: '>=18.17.0'}
+ peerDependencies:
+ next: ^13.5.7 || ^14.2.25 || ^15.2.3 || ^16
+ react: ^18.0.0 || ^19.0.0 || ^19.0.0-0
+ react-dom: ^18.0.0 || ^19.0.0 || ^19.0.0-0
+
+ '@clerk/shared@3.37.0':
+ resolution: {integrity: sha512-1CSKRebdxqihbqWj1kpmdBn6ChDYTMqGlPJQc1btbJ/OW57v7CR8i/vjhgHUOLavAF1Zl40h7Yi+9rjA5bYNHQ==}
engines: {node: '>=18.17.0'}
peerDependencies:
react: ^18.0.0 || ^19.0.0 || ^19.0.0-0
@@ -543,8 +558,8 @@ packages:
react-dom:
optional: true
- '@clerk/types@4.92.0':
- resolution: {integrity: sha512-+bUiHjqVXEHJIOOhshIy3uYDF/c4/yNc2BPfgPTXxxsbz/2wG0XUx0PL+mxUPiruPZOD+D63AtmORuFW3yBa2w==}
+ '@clerk/types@4.101.4':
+ resolution: {integrity: sha512-IZSonY7jXtctBcYg2vLswHOe00WkbBrnEmJAGNHU/r1KJ3MLnH5t4GMPFeRv/1yUtQ1tZAkvPO68gcRkS5QQlw==}
engines: {node: '>=18.17.0'}
'@connectrpc/connect-web@2.0.0-rc.3':
@@ -7081,18 +7096,39 @@ snapshots:
'@bufbuild/protobuf@2.9.0': {}
- '@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ '@clerk/backend@2.25.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ dependencies:
+ '@clerk/shared': 3.37.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/types': 4.101.4(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ cookie: 1.0.2
+ standardwebhooks: 1.0.0
+ tslib: 2.8.1
+ transitivePeerDependencies:
+ - react
+ - react-dom
+
+ '@clerk/clerk-react@5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
dependencies:
- '@clerk/shared': 3.27.3(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
- '@clerk/types': 4.92.0
+ '@clerk/shared': 3.37.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
react: 19.2.1
react-dom: 19.2.1(react@19.2.1)
tslib: 2.8.1
- optional: true
- '@clerk/shared@3.27.3(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ '@clerk/nextjs@6.35.6(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
dependencies:
- '@clerk/types': 4.92.0
+ '@clerk/backend': 2.25.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/clerk-react': 5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/shared': 3.37.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/types': 4.101.4(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ next: 16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ react: 19.2.1
+ react-dom: 19.2.1(react@19.2.1)
+ server-only: 0.0.1
+ tslib: 2.8.1
+
+ '@clerk/shared@3.37.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ dependencies:
+ csstype: 3.1.3
dequal: 2.0.3
glob-to-regexp: 0.4.1
js-cookie: 3.0.5
@@ -7101,12 +7137,13 @@ snapshots:
optionalDependencies:
react: 19.2.1
react-dom: 19.2.1(react@19.2.1)
- optional: true
- '@clerk/types@4.92.0':
+ '@clerk/types@4.101.4(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
dependencies:
- csstype: 3.1.3
- optional: true
+ '@clerk/shared': 3.37.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ transitivePeerDependencies:
+ - react
+ - react-dom
'@connectrpc/connect-web@2.0.0-rc.3(@bufbuild/protobuf@2.9.0)(@connectrpc/connect@2.0.0-rc.3(@bufbuild/protobuf@2.9.0))':
dependencies:
@@ -7117,12 +7154,12 @@ snapshots:
dependencies:
'@bufbuild/protobuf': 2.9.0
- '@convex-dev/auth@0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)':
+ '@convex-dev/auth@0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)':
dependencies:
'@auth/core': 0.37.4
'@oslojs/crypto': 1.0.1
'@oslojs/encoding': 1.1.0
- convex: 1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
+ convex: 1.30.0(@clerk/clerk-react@5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
cookie: 1.0.2
is-network-error: 1.3.0
jose: 5.10.0
@@ -10623,12 +10660,12 @@ snapshots:
convert-source-map@2.0.0: {}
- convex@1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1):
+ convex@1.30.0(@clerk/clerk-react@5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1):
dependencies:
esbuild: 0.25.4
prettier: 3.7.4
optionalDependencies:
- '@clerk/clerk-react': 5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/clerk-react': 5.57.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
react: 19.2.1
cookie-signature@1.0.6: {}
@@ -10795,7 +10832,7 @@ snapshots:
dom-helpers@5.2.1:
dependencies:
'@babel/runtime': 7.28.4
- csstype: 3.1.3
+ csstype: 3.2.3
dotenv@16.6.1: {}
@@ -12374,8 +12411,7 @@ snapshots:
'@types/react': 19.2.7
react: 19.2.1
- js-cookie@3.0.5:
- optional: true
+ js-cookie@3.0.5: {}
js-tokens@4.0.0: {}
@@ -13757,8 +13793,7 @@ snapshots:
statuses@2.0.2: {}
- std-env@3.9.0:
- optional: true
+ std-env@3.9.0: {}
stop-iteration-iterator@1.1.0:
dependencies:
@@ -13895,7 +13930,6 @@ snapshots:
dequal: 2.0.3
react: 19.2.1
use-sync-external-store: 1.6.0(react@19.2.1)
- optional: true
synckit@0.11.11:
dependencies:
|
|
🚀 Launching Scrapybara desktop... |
|
❌ Something went wrong: |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/express-4.22.1
branch
from
24741c3 to
8e5c0a9
Compare
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered development platform that enables users to create web applications via an interactive, chat-based interface. Built with Next.js, React, and TypeScript, it includes features such as real-time code previews, file explorers, and AI-driven project generation, all integrated with various backend services like Convex, Clerk for authentication, and Inngest for background processing. PR ChangesThis pull request bumps the express dependency from version 4.21.2 to 4.22.1, along with several related dependency version updates reflected in the pnpm-lock.yaml file. Although this update is primarily backend-focused and addresses potential security and performance improvements, it may indirectly affect user-facing error handling and server responses. Setup Instructions
Generated Test Cases1: Home Page Loads Successfully ❗️❗️❗️Description: Verifies that the home page loads properly, ensuring that no breaking change in express affects the delivery of the initial UI. This is a basic sanity test for user access. Prerequisites: Steps:
Expected Result: The home page should load without errors, displaying all key visual elements, navigation, and content as expected. 2: User Sign-In Flow ❗️❗️❗️Description: Tests the sign-in functionality to ensure that authentication routes and UI components function correctly after the express upgrade. Prerequisites:
Steps:
Expected Result: The sign-in process completes without errors, and the user is authenticated and redirected to the dashboard or appropriate landing page. 3: File Explorer Functionality in Project Dashboard ❗️❗️Description: Ensures that the file explorer component in the project dashboard loads and functions correctly, verifying that UI components relying on server responses work as expected. Prerequisites:
Steps:
Expected Result: The file explorer loads correctly, displays the list of project files, and allows the user to select a file to view its contents without any errors. 4: Error Page Handling for Non-Existent Routes ❗️❗️❗️Description: Verifies that the appropriate error page is displayed when a user navigates to a route that does not exist, ensuring that express error handling is working as expected. Prerequisites: Steps:
Expected Result: A user-friendly error page (e.g., a 404 page) should display, informing the user that the requested page was not found. The layout and styling should match the application’s design for error states. 5: Navigation Menu Functionality ❗️❗️Description: Checks that the header navigation menu links work correctly, ensuring that the express route changes propagate properly to the UI. Prerequisites:
Steps:
Expected Result: Each navigation link should trigger a route change, and the corresponding page should load with proper layout and content, confirming that the express-based routing and error handling behavior remains intact. Raw Changes AnalyzedFile: pnpm-lock.yaml
Changes:
@@ -12,9 +12,12 @@ importers:
.:
dependencies:
+ '@clerk/nextjs':
+ specifier: ^6.35.6
+ version: 6.36.0(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
'@convex-dev/auth':
specifier: ^0.0.90
- version: 0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)
+ version: 0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)
'@databuddy/sdk':
specifier: ^2.2.1
version: 2.3.0(@babel/core@7.28.4)(@babel/template@7.27.2)(@types/react@19.2.7)(react@19.2.1)
@@ -26,28 +29,25 @@ importers:
version: 3.10.0(react-hook-form@7.68.0(react@19.2.1))
'@inngest/agent-kit':
specifier: ^0.13.1
- version: 0.13.2(inngest@3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13))(zod@4.1.13)
+ version: 0.13.2(inngest@3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13))(zod@4.1.13)
'@inngest/realtime':
specifier: ^0.4.4
- version: 0.4.4(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(typescript@5.9.3)
+ version: 0.4.4(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(typescript@5.9.3)
'@opentelemetry/api':
specifier: ^1.9.0
version: 1.9.0
'@opentelemetry/core':
- specifier: ^2.2.0
- version: 2.2.0(@opentelemetry/api@1.9.0)
+ specifier: 1.30.0
+ version: 1.30.0(@opentelemetry/api@1.9.0)
'@opentelemetry/resources':
- specifier: ^2.2.0
- version: 2.2.0(@opentelemetry/api@1.9.0)
+ specifier: 1.30.0
+ version: 1.30.0(@opentelemetry/api@1.9.0)
'@opentelemetry/sdk-trace-base':
- specifier: ^2.2.0
- version: 2.2.0(@opentelemetry/api@1.9.0)
+ specifier: 1.30.0
+ version: 1.30.0(@opentelemetry/api@1.9.0)
'@opentelemetry/semantic-conventions':
specifier: ^1.37.0
version: 1.37.0
- '@polar-sh/sdk':
- specifier: ^0.41.3
- version: 0.41.5
'@radix-ui/react-accordion':
specifier: ^1.2.12
version: 1.2.12(@types/react-dom@19.2.3(@types/react@19.2.7))(@types/react@19.2.7)(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
@@ -128,7 +128,7 @@ importers:
version: 1.2.8(@types/react-dom@19.2.3(@types/react@19.2.7))(@types/react@19.2.7)(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
'@sentry/nextjs':
specifier: ^10.22.0
- version: 10.28.0(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@2.2.0(@opentelemetry/api@1.9.0))(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(webpack@5.102.1)
+ version: 10.28.0(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@1.30.0(@opentelemetry/api@1.9.0))(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(webpack@5.102.1)
'@tanstack/react-query':
specifier: ^5.90.6
version: 5.90.11(react@19.2.1)
@@ -175,8 +175,8 @@ importers:
specifier: ^1.1.1
version: 1.1.1(@types/react-dom@19.2.3(@types/react@19.2.7))(@types/react@19.2.7)(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
convex:
- specifier: ^1.29.0
- version: 1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
+ specifier: ^1.30.0
+ version: 1.30.0(@clerk/clerk-react@5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
csv-parse:
specifier: ^6.1.0
version: 6.1.0
@@ -197,7 +197,7 @@ importers:
version: 4.4.1
inngest:
specifier: ^3.46.0
- version: 3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13)
+ version: 3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13)
input-otp:
specifier: ^1.4.2
version: 1.4.2(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
@@ -524,15 +524,27 @@ packages:
'@bufbuild/protobuf@2.9.0':
resolution: {integrity: sha512-rnJenoStJ8nvmt9Gzye8nkYd6V22xUAnu4086ER7h1zJ508vStko4pMvDeQ446ilDTFpV5wnoc5YS7XvMwwMqA==}
- '@clerk/clerk-react@5.51.0':
- resolution: {integrity: sha512-jBreKiUS4DKm+JUIt59B1699aRr3wQmQ1O+DlWCEY3iEz+F6ETir1SJcRNG5mHVoA9EGn+m93USJSUWZBRG8yQ==}
+ '@clerk/backend@2.25.1':
+ resolution: {integrity: sha512-L5JeWWuMAxBfxip6RKglBhKVywykJwMaSo2NkW8pfjM9INQ/JtpXTlVl5SKSv5v43vSkKxYeqKXkXyNgtxRPaQ==}
+ engines: {node: '>=18.17.0'}
+
+ '@clerk/clerk-react@5.58.0':
+ resolution: {integrity: sha512-UTHpoBnkb/4VoXQ/+72cer798jbt9GmvAsY/6GFcUz9oC/y9wiAS1RXGnrTkFKy7Q2DAeAcxYdb4ao4TEKrLBg==}
+ engines: {node: '>=18.17.0'}
+ peerDependencies:
+ react: ^18.0.0 || ^19.0.0 || ^19.0.0-0
+ react-dom: ^18.0.0 || ^19.0.0 || ^19.0.0-0
+
+ '@clerk/nextjs@6.36.0':
+ resolution: {integrity: sha512-OXxFdOH7jdzGAiBtedwA2hP5IFvxgojH9wnSeCrYA77RXV3YF10ujia/tPU3C6iE0xT8U/WMCd7uSp6XmeWLHQ==}
engines: {node: '>=18.17.0'}
peerDependencies:
+ next: ^13.5.7 || ^14.2.25 || ^15.2.3 || ^16
react: ^18.0.0 || ^19.0.0 || ^19.0.0-0
react-dom: ^18.0.0 || ^19.0.0 || ^19.0.0-0
- '@clerk/shared@3.27.3':
- resolution: {integrity: sha512-OJqWwlQGi6XMVWJVtY1YmOESAkEAflDrynFSjwQQ/sC8c4hmUukIq07XTOlcv6j4u1i4akhtNwy40B1qiRrLdg==}
+ '@clerk/shared@3.38.0':
+ resolution: {integrity: sha512-9R63kyHXq4DntdQXWxwpFZSq04AR8rby0cqAnUfTsAddyxQOmyjgHZADKkrMYUbhGiJnLBysUmZBPyVizjaopg==}
engines: {node: '>=18.17.0'}
peerDependencies:
react: ^18.0.0 || ^19.0.0 || ^19.0.0-0
@@ -543,8 +555,8 @@ packages:
react-dom:
optional: true
- '@clerk/types@4.92.0':
- resolution: {integrity: sha512-+bUiHjqVXEHJIOOhshIy3uYDF/c4/yNc2BPfgPTXxxsbz/2wG0XUx0PL+mxUPiruPZOD+D63AtmORuFW3yBa2w==}
+ '@clerk/types@4.101.5':
+ resolution: {integrity: sha512-LEfEizGRM0hN/8GHaia8EIf7kcTHKh2R/Ebj7n1zETB88HrCrM6mvTVv/fqpf5203F1GsCR/UU2l18EOClfWGA==}
engines: {node: '>=18.17.0'}
'@connectrpc/connect-web@2.0.0-rc.3':
@@ -1405,6 +1417,12 @@ packages:
peerDependencies:
'@opentelemetry/api': '>=1.0.0 <1.10.0'
+ '@opentelemetry/core@1.30.0':
+ resolution: {integrity: sha512-Q/3u/K73KUjTCnFUP97ZY+pBjQ1kPEgjOfXj/bJl8zW7GbXdkw6cwuyZk6ZTXkVgCBsYRYUzx4fvYK1jxdb9MA==}
+ engines: {node: '>=14'}
+ peerDependencies:
+ '@opentelemetry/api': '>=1.0.0 <1.10.0'
+
'@opentelemetry/core@2.2.0':
resolution: {integrity: sha512-FuabnnUm8LflnieVxs6eP7Z383hgQU4W1e3KJS6aOG3RxWxcHyBxH8fDMHNgu/gFx/M2jvTOW/4/PHhLz6bjWw==}
engines: {node: ^18.19.0 || >=20.6.0}
@@ -1817,6 +1835,12 @@ packages:
peerDependencies:
'@opentelemetry/api': ^1.0.0
+ '@opentelemetry/resources@1.30.0':
+ resolution: {integrity: sha512-5mGMjL0Uld/99t7/pcd7CuVtJbkARckLVuiOX84nO8RtLtIz0/J6EOHM2TGvPZ6F4K+XjUq13gMx14w80SVCQg==}
+ engines: {node: '>=14'}
+ peerDependencies:
+ '@opentelemetry/api': '>=1.0.0 <1.10.0'
+
'@opentelemetry/resources@2.2.0':
resolution: {integrity: sha512-1pNQf/JazQTMA0BiO5NINUzH0cbLbbl7mntLa4aJNmCCXSj0q03T5ZXXL0zw4G55TjdL9Tz32cznGClf+8zr5A==}
engines: {node: ^18.19.0 || >=20.6.0}
@@ -1841,6 +1865,12 @@ packages:
peerDependencies:
'@opentelemetry/api': '>=1.3.0 <1.10.0'
+ '@opentelemetry/sdk-trace-base@1.30.0':
+ resolution: {integrity: sha512-RKQDaDIkV7PwizmHw+rE/FgfB2a6MBx+AEVVlAHXRG1YYxLiBpPX2KhmoB99R5vA4b72iJrjle68NDWnbrE9Dg==}
+ engines: {node: '>=14'}
+ peerDependencies:
+ '@opentelemetry/api': '>=1.0.0 <1.10.0'
+
'@opentelemetry/sdk-trace-base@2.2.0':
resolution: {integrity: sha512-xWQgL0Bmctsalg6PaXExmzdedSp3gyKV8mQBwK/j9VGdCDu2fmXIb2gAehBKbkXCpJ4HPkgv3QfoJWRT4dHWbw==}
engines: {node: ^18.19.0 || >=20.6.0}
@@ -1853,6 +1883,10 @@ packages:
peerDependencies:
'@opentelemetry/api': '>=1.0.0 <1.10.0'
+ '@opentelemetry/semantic-conventions@1.28.0':
+ resolution: {integrity: sha512-lp4qAiMTD4sNWW4DbKLBkfiMZ4jbAboJIGOQr5DvciMRI494OapieI9qiODpOt0XBr1LjIDy1xAGAnVs5supTA==}
+ engines: {node: '>=14'}
+
'@opentelemetry/semantic-conventions@1.37.0':
resolution: {integrity: sha512-JD6DerIKdJGmRp4jQyX5FlrQjA4tjOw1cvfsPAZXfOOEErMUHjPcPSICS+6WnM0nB0efSFARh0KAZss+bvExOA==}
engines: {node: '>=14'}
@@ -1886,9 +1920,6 @@ packages:
resolution: {integrity: sha512-QNqXyfVS2wm9hweSYD2O7F0G06uurj9kZ96TRQE5Y9hU7+tgdZwIkbAKc5Ocy1HxEY2kuDQa6cQ1WRs/O5LFKA==}
engines: {node: ^12.20.0 || ^14.18.0 || >=16.0.0}
- '@polar-sh/sdk@0.41.5':
- resolution: {integrity: sha512-E+VoVV+WvebZKmj+KZ/fj1byBZbG7J8hHyzYD9kktvAToigPM19sywo2tFCHeb44aWGCVACMOP8r31e6je7dxA==}
-
'@prisma/instrumentation@6.19.0':
resolution: {integrity: sha512-QcuYy25pkXM8BJ37wVFBO7Zh34nyRV1GOb2n3lPkkbRYfl4hWl3PTcImP41P0KrzVXfa/45p6eVCos27x3exIg==}
peerDependencies:
@@ -7081,18 +7112,39 @@ snapshots:
'@bufbuild/protobuf@2.9.0': {}
- '@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ '@clerk/backend@2.25.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ dependencies:
+ '@clerk/shared': 3.38.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/types': 4.101.5(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ cookie: 1.0.2
+ standardwebhooks: 1.0.0
+ tslib: 2.8.1
+ transitivePeerDependencies:
+ - react
+ - react-dom
+
+ '@clerk/clerk-react@5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
dependencies:
- '@clerk/shared': 3.27.3(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
- '@clerk/types': 4.92.0
+ '@clerk/shared': 3.38.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
react: 19.2.1
react-dom: 19.2.1(react@19.2.1)
tslib: 2.8.1
- optional: true
- '@clerk/shared@3.27.3(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ '@clerk/nextjs@6.36.0(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
dependencies:
- '@clerk/types': 4.92.0
+ '@clerk/backend': 2.25.1(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/clerk-react': 5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/shared': 3.38.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/types': 4.101.5(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ next: 16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ react: 19.2.1
+ react-dom: 19.2.1(react@19.2.1)
+ server-only: 0.0.1
+ tslib: 2.8.1
+
+ '@clerk/shared@3.38.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
+ dependencies:
+ csstype: 3.1.3
dequal: 2.0.3
glob-to-regexp: 0.4.1
js-cookie: 3.0.5
@@ -7101,12 +7153,13 @@ snapshots:
optionalDependencies:
react: 19.2.1
react-dom: 19.2.1(react@19.2.1)
- optional: true
- '@clerk/types@4.92.0':
+ '@clerk/types@4.101.5(react-dom@19.2.1(react@19.2.1))(react@19.2.1)':
dependencies:
- csstype: 3.1.3
- optional: true
+ '@clerk/shared': 3.38.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ transitivePeerDependencies:
+ - react
+ - react-dom
'@connectrpc/connect-web@2.0.0-rc.3(@bufbuild/protobuf@2.9.0)(@connectrpc/connect@2.0.0-rc.3(@bufbuild/protobuf@2.9.0))':
dependencies:
@@ -7117,12 +7170,12 @@ snapshots:
dependencies:
'@bufbuild/protobuf': 2.9.0
- '@convex-dev/auth@0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)':
+ '@convex-dev/auth@0.0.90(@auth/core@0.37.4)(convex@1.30.0(@clerk/clerk-react@5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1))(react@19.2.1)':
dependencies:
'@auth/core': 0.37.4
'@oslojs/crypto': 1.0.1
'@oslojs/encoding': 1.1.0
- convex: 1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
+ convex: 1.30.0(@clerk/clerk-react@5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)
cookie: 1.0.2
is-network-error: 1.3.0
jose: 5.10.0
@@ -7510,14 +7563,14 @@ snapshots:
'@img/sharp-win32-x64@0.34.4':
optional: true
- '@inngest/agent-kit@0.13.2(inngest@3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13))(zod@4.1.13)':
+ '@inngest/agent-kit@0.13.2(inngest@3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13))(zod@4.1.13)':
dependencies:
'@dmitryrechkin/json-schema-to-zod': 1.0.1
'@inngest/ai': 0.1.6
'@modelcontextprotocol/sdk': 1.19.1
eventsource: 3.0.7
express: 4.21.2
- inngest: 3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13)
+ inngest: 3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13)
xxhashjs: 0.2.2
zod: 4.1.13
transitivePeerDependencies:
@@ -7528,11 +7581,11 @@ snapshots:
'@types/node': 22.18.8
typescript: 5.9.3
- '@inngest/realtime@0.4.4(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(typescript@5.9.3)':
+ '@inngest/realtime@0.4.4(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(typescript@5.9.3)':
dependencies:
'@standard-schema/spec': 1.0.0
debug: 4.4.3
- inngest: 3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@3.25.76)
+ inngest: 3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@3.25.76)
react: 19.2.1
zod: 3.25.76
transitivePeerDependencies:
@@ -7878,10 +7931,10 @@ snapshots:
'@opentelemetry/api@1.9.0': {}
- '@opentelemetry/auto-instrumentations-node@0.67.2(@opentelemetry/api@1.9.0)(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))':
+ '@opentelemetry/auto-instrumentations-node@0.67.2(@opentelemetry/api@1.9.0)(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))':
dependencies:
'@opentelemetry/api': 1.9.0
- '@opentelemetry/core': 2.2.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/core': 1.30.0(@opentelemetry/api@1.9.0)
'@opentelemetry/instrumentation': 0.208.0(@opentelemetry/api@1.9.0)
'@opentelemetry/instrumentation-amqplib': 0.55.0(@opentelemetry/api@1.9.0)
'@opentelemetry/instrumentation-aws-lambda': 0.61.0(@opentelemetry/api@1.9.0)
@@ -7943,6 +7996,11 @@ snapshots:
dependencies:
'@opentelemetry/api': 1.9.0
+ '@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0)':
+ dependencies:
+ '@opentelemetry/api': 1.9.0
+ '@opentelemetry/semantic-conventions': 1.28.0
+
'@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0)':
dependencies:
'@opentelemetry/api': 1.9.0
@@ -8514,6 +8572,12 @@ snapshots:
- encoding
- supports-color
+ '@opentelemetry/resources@1.30.0(@opentelemetry/api@1.9.0)':
+ dependencies:
+ '@opentelemetry/api': 1.9.0
+ '@opentelemetry/core': 1.30.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/semantic-conventions': 1.28.0
+
'@opentelemetry/resources@2.2.0(@opentelemetry/api@1.9.0)':
dependencies:
'@opentelemetry/api': 1.9.0
@@ -8561,6 +8625,13 @@ snapshots:
transitivePeerDependencies:
- supports-color
+ '@opentelemetry/sdk-trace-base@1.30.0(@opentelemetry/api@1.9.0)':
+ dependencies:
+ '@opentelemetry/api': 1.9.0
+ '@opentelemetry/core': 1.30.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/resources': 1.30.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/semantic-conventions': 1.28.0
+
'@opentelemetry/sdk-trace-base@2.2.0(@opentelemetry/api@1.9.0)':
dependencies:
'@opentelemetry/api': 1.9.0
@@ -8575,6 +8646,8 @@ snapshots:
'@opentelemetry/core': 2.2.0(@opentelemetry/api@1.9.0)
'@opentelemetry/sdk-trace-base': 2.2.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/semantic-conventions@1.28.0': {}
+
'@opentelemetry/semantic-conventions@1.37.0': {}
'@opentelemetry/sql-common@0.41.2(@opentelemetry/api@1.9.0)':
@@ -8602,11 +8675,6 @@ snapshots:
'@pkgr/core@0.2.9': {}
- '@polar-sh/sdk@0.41.5':
- dependencies:
- standardwebhooks: 1.0.0
- zod: 4.1.13
-
'@prisma/instrumentation@6.19.0(@opentelemetry/api@1.9.0)':
dependencies:
'@opentelemetry/api': 1.9.0
@@ -9488,7 +9556,7 @@ snapshots:
'@sentry/core@10.28.0': {}
- '@sentry/nextjs@10.28.0(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@2.2.0(@opentelemetry/api@1.9.0))(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(webpack@5.102.1)':
+ '@sentry/nextjs@10.28.0(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@1.30.0(@opentelemetry/api@1.9.0))(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1)(webpack@5.102.1)':
dependencies:
'@opentelemetry/api': 1.9.0
'@opentelemetry/semantic-conventions': 1.37.0
@@ -9497,7 +9565,7 @@ snapshots:
'@sentry/bundler-plugin-core': 4.6.1
'@sentry/core': 10.28.0
'@sentry/node': 10.28.0
- '@sentry/opentelemetry': 10.28.0(@opentelemetry/api@1.9.0)(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/semantic-conventions@1.37.0)
+ '@sentry/opentelemetry': 10.28.0(@opentelemetry/api@1.9.0)(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@1.30.0(@opentelemetry/api@1.9.0))(@opentelemetry/semantic-conventions@1.37.0)
'@sentry/react': 10.28.0(react@19.2.1)
'@sentry/vercel-edge': 10.28.0
'@sentry/webpack-plugin': 4.6.1(webpack@5.102.1)
@@ -9570,6 +9638,15 @@ snapshots:
transitivePeerDependencies:
- supports-color
+ '@sentry/opentelemetry@10.28.0(@opentelemetry/api@1.9.0)(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@1.30.0(@opentelemetry/api@1.9.0))(@opentelemetry/semantic-conventions@1.37.0)':
+ dependencies:
+ '@opentelemetry/api': 1.9.0
+ '@opentelemetry/context-async-hooks': 2.2.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/core': 1.30.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/sdk-trace-base': 1.30.0(@opentelemetry/api@1.9.0)
+ '@opentelemetry/semantic-conventions': 1.37.0
+ '@sentry/core': 10.28.0
+
'@sentry/opentelemetry@10.28.0(@opentelemetry/api@1.9.0)(@opentelemetry/context-async-hooks@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/sdk-trace-base@2.2.0(@opentelemetry/api@1.9.0))(@opentelemetry/semantic-conventions@1.37.0)':
dependencies:
'@opentelemetry/api': 1.9.0
@@ -10623,12 +10700,12 @@ snapshots:
convert-source-map@2.0.0: {}
- convex@1.30.0(@clerk/clerk-react@5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1):
+ convex@1.30.0(@clerk/clerk-react@5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(react@19.2.1):
dependencies:
esbuild: 0.25.4
prettier: 3.7.4
optionalDependencies:
- '@clerk/clerk-react': 5.51.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
+ '@clerk/clerk-react': 5.58.0(react-dom@19.2.1(react@19.2.1))(react@19.2.1)
react: 19.2.1
cookie-signature@1.0.6: {}
@@ -10795,7 +10872,7 @@ snapshots:
dom-helpers@5.2.1:
dependencies:
'@babel/runtime': 7.28.4
- csstype: 3.1.3
+ csstype: 3.2.3
dotenv@16.6.1: {}
@@ -11762,13 +11839,13 @@ snapshots:
inline-style-parser@0.2.7: {}
- inngest@3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@3.25.76):
+ inngest@3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@3.25.76):
dependencies:
'@bufbuild/protobuf': 2.9.0
'@inngest/ai': 0.1.6
'@jpwilliams/waitgroup': 2.1.1
'@opentelemetry/api': 1.9.0
- '@opentelemetry/auto-instrumentations-node': 0.67.2(@opentelemetry/api@1.9.0)(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))
+ '@opentelemetry/auto-instrumentations-node': 0.67.2(@opentelemetry/api@1.9.0)(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))
'@opentelemetry/context-async-hooks': 2.1.0(@opentelemetry/api@1.9.0)
'@opentelemetry/exporter-trace-otlp-http': 0.208.0(@opentelemetry/api@1.9.0)
'@opentelemetry/instrumentation': 0.204.0(@opentelemetry/api@1.9.0)
@@ -11797,13 +11874,13 @@ snapshots:
- encoding
- supports-color
- inngest@3.46.0(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13):
+ inngest@3.46.0(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))(express@5.1.0)(next@16.0.7(@babel/core@7.28.4)(@opentelemetry/api@1.9.0)(react-dom@19.2.1(react@19.2.1))(react@19.2.1))(typescript@5.9.3)(zod@4.1.13):
dependencies:
'@bufbuild/protobuf': 2.9.0
'@inngest/ai': 0.1.6
'@jpwilliams/waitgroup': 2.1.1
'@opentelemetry/api': 1.9.0
- '@opentelemetry/auto-instrumentations-node': 0.67.2(@opentelemetry/api@1.9.0)(@opentelemetry/core@2.2.0(@opentelemetry/api@1.9.0))
+ '@opentelemetry/auto-instrumentations-node': 0.67.2(@opentelemetry/api@1.9.0)(@opentelemetry/core@1.30.0(@opentelemetry/api@1.9.0))
'@opentelemetry/context-async-hooks': 2.1.0(@opentelemetry/api@1.9.0)
'@opentelemetry/exporter-trace-otlp-http': 0.208.0(@opentelemetry/api@1.9.0)
'@opentelemetry/instrumentation': 0.204.0(@opentelemetry/api@1.9.0)
@@ -12374,8 +12451,7 @@ snapshots:
'@types/react': 19.2.7
react: 19.2.1
- js-cookie@3.0.5:
- optional: true
+ js-cookie@3.0.5: {}
js-tokens@4.0.0: {}
@@ -13757,8 +13833,7 @@ snapshots:
statuses@2.0.2: {}
- std-env@3.9.0:
- optional: true
+ std-env@3.9.0: {}
stop-iteration-iterator@1.1.0:
dependencies:
@@ -13895,7 +13970,6 @@ snapshots:
dequal: 2.0.3
react: 19.2.1
use-sync-external-store: 1.6.0(react@19.2.1)
- optional: true
synckit@0.11.11:
dependencies:
|
|
🚀 Launching Scrapybara desktop... |
|
❌ Something went wrong: |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/express-4.22.1
branch
from
8e5c0a9 to
19f736b
Compare
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered web development platform that enables users to create, manage, and preview web applications in real-time. It features a live preview interface, conversational project development with AI agents, integrated authentication, and various UI components for project management and file exploration. PR ChangesThis PR bumps express from 4.21.2 to 4.22.1. Although the update is primarily a backend dependency upgrade for security fixes and performance improvements, it has the potential to indirectly affect the way errors are handled and responses are formatted in the application. It is important to verify that user-facing routes and error handling in the UI remain consistent and unaffected by this update. Setup Instructions
Generated Test Cases1: Home Page Loads and Renders Properly ❗️❗️❗️Description: This test ensures that the home page loads correctly, displaying the primary UI elements such as the header, logo, and navigation elements. It validates that the express bump has not affected the core routing or server response rendering. Prerequisites: Steps:
Expected Result: The home page should render quickly and correctly, displaying the application header, logo, and navigation links without any layout issues or missing elements. 2: Navigation Menu User Flow ❗️❗️Description: This test checks that the navigation links function as expected. It verifies that transitioning between sections (e.g., the Showcase or Solutions page) works seamlessly after the express update. Prerequisites:
Steps:
Expected Result: The application should navigate to the selected page without errors, and the content for that section should be displayed correctly. 3: Auth Modal Display on Sign In ❗️❗️❗️Description: This test ensures that the authentication modal (e.g., for signing in via Clerk) is triggered correctly. It checks for proper UI behavior when a user initiates a sign-in action. Prerequisites:
Steps:
Expected Result: The sign-in modal should be displayed with appropriate input fields and messaging, allowing the user to proceed with authentication. 4: Error Page Display for Invalid Route ❗️❗️❗️Description: This test validates that navigating to an invalid or non-existent route results in a proper error page (e.g., a 404 error page). This ensures that the error handling mechanism remains intact post-upgrade. Prerequisites: Steps:
Expected Result: The application should display a user-friendly 404 error page indicating that the requested page was not found. Raw Changes Analyzed |
|
🚀 Launching Scrapybara desktop... |
|
❌ Something went wrong: |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/express-4.22.1
branch
from
19f736b to
9ed522f
Compare
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered development platform that lets users create web applications by interacting with AI agents in real-time sandboxes. The platform provides a split-pane interface for live code preview, file explorers, and a conversational development experience with integrated authentication and project management. PR ChangesThis PR bumps the Express version from 4.21.2 to 4.22.1. Although this is a backend dependency update, Express serves as the foundation for handling HTTP requests and errors. The update includes security fixes and changes in error handling behavior (e.g., method functions with no path should error). It is important to perform end-to-end UI tests to ensure that routing, error displays, and user interactions are not impacted by this backend change. Setup Instructions
Generated Test Cases1: Home Page Loads Successfully ❗️❗️❗️Description: Verify that the application home page loads correctly, displaying key UI components such as navigation, file explorer, and live preview elements. This confirms that the server is handling requests correctly after the Express update. Prerequisites: Steps:
Expected Result: The home page should display all expected elements (navigation, file explorer, live preview, etc.) without any errors. Page content loads completely and correctly. 2: Error Handling on Invalid Route ❗️❗️❗️Description: Test that navigating to an invalid URL displays a friendly error (404) page. This assesses that Express handles unknown routes properly and that the UI gracefully informs the user of navigation errors. Prerequisites: Steps:
Expected Result: A user-friendly 404 page should be displayed with a clear message indicating that the page was not found. The error page should provide navigation options to guide the user back to existing pages. 3: Navigation to Sign In Page ❗️❗️Description: Ensure that users can navigate to the sign in page successfully, which is critical for accessing personalized features. This test verifies the integrity of routing and UI elements post-Express update. Prerequisites: Steps:
Expected Result: The sign in page should load displaying the proper UI elements, including input fields and sign in button. Client-side validation messages (if any) should appear when required fields are empty. 4: Project Creation Workflow ❗️❗️❗️Description: Test the project creation workflow from the user's perspective. This ensures that after the Express update, server-side request handling still supports creating projects and subsequent UI updates. Prerequisites:
Steps:
Expected Result: The new project should be created successfully. The UI should display a success notification and the project listing should include the newly created project without any errors. Raw Changes Analyzed |
|
🚀 Launching Scrapybara desktop... |
|
❌ Something went wrong: |
Dependabot couldn't find the original pull request head commit, 8e5c0a9.
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/express-4.22.1
branch
from
9ed522f to
56bcac9
Compare
CodeCapy Review ₍ᐢ•(ܫ)•ᐢ₎
Codebase SummaryZapDev is an AI-powered development platform that enables users to build web applications through a conversational interface. It uses a Next.js frontend with React, TypeScript, and Tailwind CSS, integrated with a backend powered by Express, Convex, and tRPC. The application heavily relies on real-time updates, live previews, and robust error handling to give users immediate feedback during their development process. PR ChangesThis pull request bumps express from version 4.21.2 to 4.22.1. The update includes several internal fixes and a reversion of a security patch for CVE-2024-51999. Although the changes are largely internal to express, they may affect the behavior of error responses or routing in the backend, which in turn can affect user-facing error pages and API-driven interactions. Setup Instructions
Generated Test Cases1: Home Page Loads Successfully ❗️❗️❗️Description: Verifies that the core user journey starting at the home page is unaffected by the Express version bump. This confirms that the upgrade does not disrupt the initial application load or navigation. Prerequisites:
Steps:
Expected Result: The home page and subsequent navigation pages load without error. All UI components are rendered correctly and routing works seamlessly. 2: 404 Error Page Displays Correctly ❗️❗️❗️Description: Checks that when a user navigates to a non-existent route, the custom 404 error page is displayed. This ensures that route handling and error messaging remain intact despite the Express upgrade. Prerequisites:
Steps:
Expected Result: A custom 404 error page is displayed with a message indicating that the page could not be found. The layout and styling should be consistent with the rest of the site. 3: API Error Handling and Feedback Display ❗️❗️Description: Simulates an API failure scenario to verify that the UI properly handles and displays error messages based on backend responses. Changes in Express error handling may affect API response formatting. Prerequisites:
Steps:
Expected Result: The UI should show a clear error message without breaking the application layout. The error message should encourage the user to retry or check their input, consistent with the design of the error handling components. 4: Navigation Consistency After Express Update ❗️❗️Description: Ensures that overall navigation and redirection work correctly. Although the Express bump is a backend change, it could affect any server-side redirection or error middleware that influences user navigation. Prerequisites:
Steps:
Expected Result: The application navigates consistently between pages with proper redirection and without displaying backend error messages. UI components remain intact throughout the user journey. Raw Changes Analyzed |
|
🚀 Launching Scrapybara desktop... |
|
❌ Something went wrong: |
Bumps express from 4.21.2 to 4.22.1.
Release notes
Sourced from express's releases.
Changelog
Sourced from express's changelog.
Commits
12fae144.22.15ddf311Revert "sec: security patch for CVE-2024-51999"49744ab4.22.0 (#6921)6e97452sec: security patch for CVE-2024-519996a23d34deps: use tilde notation forqs(#6919)8c12cdfdeps: qs@6.14.0 (#6909)7fea74fdeps: use tilde notation for certain dependencies (#6905)dac7a04chore: wider range for query test skip (#6513)997919bci: add node.js 24 to test matrix (#6506)36fb59cfix(ci): reordernpm isteps to fix ci for older node versions (#6336)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.