chore: update schemas and dependencies by felix-schultz · Pull Request #509 · TM9657/flow-like

felix-schultz · 2026-02-13T13:11:44Z

Refactored JSON schemas in desktop and macOS to improve structure and maintainability by reordering properties and removing redundant definitions.
Updated the version of @sentry/nextjs to ^10.38.0 in web, ui, and root package.json files to ensure compatibility and access to the latest features and fixes.

- Refactored JSON schemas in desktop and macOS to improve structure and maintainability by reordering properties and removing redundant definitions. - Updated the version of @sentry/nextjs to ^10.38.0 in web, ui, and root package.json files to ensure compatibility and access to the latest features and fixes.

gemini-code-assist · 2026-02-13T13:12:05Z

Summary of Changes

Hello @felix-schultz, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on essential maintenance by updating core dependencies and refining JSON schema definitions. The dependency updates ensure that the project benefits from the latest features, performance improvements, and security fixes provided by the updated libraries, particularly for Sentry integration. The schema refactoring enhances the clarity and organization of configuration files, making them easier to understand and manage.

Highlights

Dependency Updates: Updated various Rust dependencies in Cargo.lock and Cargo.toml, including sentry, sentry-tracing, sentry-tower, proc-macro-crate, base64, itertools, and reqwest to their latest versions. Also updated the @sentry/nextjs dependency to ^10.38.0 across multiple JavaScript packages (apps/desktop, apps/web, packages/ui, and the root package.json).
JSON Schema Refactoring: Refactored JSON schemas for desktop and macOS applications by reordering properties within object definitions and adjusting the placement of the ShellScopeEntryAllowedArgs definition for improved structure and maintainability.
Workspace Dependency Adoption: Migrated sentry and sentry-tracing dependencies in apps/desktop/src-tauri/Cargo.toml to use workspace inheritance, centralizing their version management.

Changelog

Cargo.lock
- Updated sentry and sentry-tracing to 0.46.2 and removed older versions.
- Updated proc-macro-crate from 1.3.1 to 3.4.0.
- Updated base64 from 0.21.7 to 0.22.1.
- Updated itertools from 0.10.5 to 0.14.0.
- Updated reqwest from 0.11.27 to 0.12.28.
Cargo.toml
- Updated sentry-tracing to 0.46.2.
- Updated sentry to 0.46.2 and added the anyhow feature.
- Updated sentry-tower to 0.46.2.
apps/desktop/package.json
- Updated @sentry/nextjs from ^9.39.0 to ^10.38.0.
apps/desktop/src-tauri/Cargo.toml
- Updated sentry to use workspace version (sentry.workspace = true).
- Updated sentry-tracing to use workspace version (sentry-tracing.workspace = true).
apps/desktop/src-tauri/gen/schemas/desktop-schema.json
- Reordered properties within properties objects for url and path definitions.
- Reordered properties within properties objects for cmd and sidecar definitions.
- Removed and re-added the ShellScopeEntryAllowedArgs definition, effectively reordering it.
apps/desktop/src-tauri/gen/schemas/macOS-schema.json
- Reordered properties within properties objects for url and path definitions.
- Reordered properties within properties objects for cmd and sidecar definitions.
- Removed and re-added the ShellScopeEntryAllowedArgs definition, effectively reordering it.
apps/web/package.json
- Updated @sentry/nextjs from ^10 to ^10.38.0.
package.json
- Added an overrides entry for @sentry/nextjs to ^10.38.0.
packages/ui/package.json
- Updated @sentry/nextjs from ^9.39.0 to ^10.38.0.

Activity

The pull request was created by felix-schultz to update dependencies and refactor JSON schemas.
No further human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request primarily focuses on updating dependencies, with a significant update to the Sentry ecosystem across both Rust and JavaScript packages, and some refactoring of JSON schemas. The changes are well-contained and improve the project's maintainability. My review includes suggestions to pin the exact versions of the updated npm packages to further enhance dependency stability.

gemini-code-assist · 2026-02-13T13:14:54Z

apps/desktop/package.json

 		"@radix-ui/react-toolbar": "^1.1.10",
 		"@radix-ui/react-tooltip": "^1.2.7",
-		"@sentry/nextjs": "^9.39.0",
+		"@sentry/nextjs": "^10.38.0",


For better dependency stability, it's a good practice to pin the exact version of dependencies, especially after a major version bump like this one from v9 to v10. This ensures that everyone on the team and in CI/CD environments uses the exact same version of the package.

Suggested change

"@sentry/nextjs": "^10.38.0",

"@sentry/nextjs": "10.38.0",

gemini-code-assist · 2026-02-13T13:14:54Z

apps/web/package.json

 		"@radix-ui/react-toolbar": "^1.1.10",
 		"@radix-ui/react-tooltip": "^1.2.7",
-		"@sentry/nextjs": "^10",
+		"@sentry/nextjs": "^10.38.0",


To prevent unexpected updates and ensure consistent builds, it's recommended to pin the exact version of this dependency instead of using a caret (^).

Suggested change

"@sentry/nextjs": "^10.38.0",

"@sentry/nextjs": "10.38.0",

gemini-code-assist · 2026-02-13T13:14:54Z

package.json

 	},
 	"workspaces": ["packages/*", "apps/*"],
+	"overrides": {
+		"@sentry/nextjs": "^10.38.0"


To ensure dependency stability across the monorepo, it's recommended to pin the exact version in the overrides section. This guarantees that all packages in the workspace resolve to the identical package version, preventing potential issues from minor version differences.

Suggested change

"@sentry/nextjs": "^10.38.0"

"@sentry/nextjs": "10.38.0"

gemini-code-assist · 2026-02-13T13:14:54Z

packages/ui/package.json

 		"@react-three/drei": "^10.7.7",
 		"@react-three/fiber": "^9.5.0",
-		"@sentry/nextjs": "^9.39.0",
+		"@sentry/nextjs": "^10.38.0",


For better dependency stability, it's a good practice to pin the exact version of dependencies, especially after a major version bump like this one from v9 to v10. This ensures that everyone on the team and in CI/CD environments uses the exact same version of the package.

Suggested change

"@sentry/nextjs": "^10.38.0",

"@sentry/nextjs": "10.38.0",

felix-schultz linked an issue Feb 13, 2026 that may be closed by this pull request

Align Sentry Dependencies #503

Closed

Merge branch 'dev' into task/503-align-sentry-dependencies

ddc5a3e

felix-schultz merged commit 4d6a633 into dev Feb 13, 2026
5 of 12 checks passed

felix-schultz deleted the task/503-align-sentry-dependencies branch February 13, 2026 13:12

gemini-code-assist bot reviewed Feb 13, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: update schemas and dependencies#509

chore: update schemas and dependencies#509
felix-schultz merged 2 commits intodevfrom
task/503-align-sentry-dependencies

felix-schultz commented Feb 13, 2026

Uh oh!

gemini-code-assist bot commented Feb 13, 2026

Uh oh!

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 13, 2026

Uh oh!

gemini-code-assist bot Feb 13, 2026

Uh oh!

gemini-code-assist bot Feb 13, 2026

Uh oh!

gemini-code-assist bot Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

felix-schultz commented Feb 13, 2026

Uh oh!

gemini-code-assist bot commented Feb 13, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant