Sync evals types

[cte]

Context

Sync copied types from the extension.

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Syncs evals types with the extension by updating dependencies, default settings, and schemas across multiple files.

• Dependencies:
  • Updated @dotenvx/dotenvx to ^1.41.0, @eslint/js to ^9.25.1, eslint to ^9.25.1, tsx to ^4.19.4, turbo to ^2.5.2, typescript-eslint to ^8.31.1 in package.json.
• Defaults:
  • Removed modelTemperature, reasoningEffort, pinnedApiConfigs, browserViewportSize, screenshotQuality, remoteBrowserEnabled, checkpointStorage, ttsEnabled, ttsSpeed, soundEnabled, soundVolume, terminalOutputLineLimit, terminalShellIntegrationTimeout, terminalCommandDelay, terminalPowershellCounter, terminalZshClearEolMark, terminalZshOhMy, terminalZshP10k, terminalZdotdir, diffEnabled, fuzzyMatchThreshold, experiments, language, telemetrySetting from rooCodeDefaults in roo-code-defaults.ts.
• Schemas:
  • Added reasoningEffortsSchema, commandExecutionStatusSchema, toolProgressStatusSchema in roo-code.ts.
  • Updated modelInfoSchema and providerSettingsSchema in roo-code.ts to include new fields like maxThinkingTokens, isPromptCacheOptional, minTokensPerCachePoint, maxCachePoints, cachableFields, tiers, openAiHostHeader, openAiLegacyFormat, enableReasoningEffort, promptCachingEnabled, diffEnabled, fuzzyMatchThreshold.
  • Added historyPreviewCollapsed, cachedChromeHostUrl to globalSettingsSchema in roo-code.ts.
  • Synced providerNames and toolNames in index.ts with roo-code.ts.

^{This description was created by for c5eb171. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: f4abe26

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

The pull request contains changes across multiple areas: updating devDependencies, refactoring settings, updating schemas, and adding documentation. If these changes are not interdependent, consider splitting them into separate pull requests for better clarity and focus. For example, the updates to devDependencies could be one pull request, while the refactoring of settings and schema updates could be another. This approach can help in reviewing and testing the changes more effectively.