Move evals into pnpm workspace, switch from SQLite to Postgres #4278
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.
Description
Long overdue, and saves a lot of duplication.
Important
Move evals into a pnpm workspace, update package names, switch to PostgreSQL, and adjust configurations and scripts accordingly.
package.jsonandpnpm-workspace.yaml.@evalsto@roo-code.package.jsonfiles to reflect new package names.@roo-code/config-eslint.@roo-code/config-typescript.drizzle.config.tsand migration files.docker-compose.ymlfor PostgreSQL setup.setup.shand Dockerfile to reflect new workspace structure.This description was created by
for 1bfc6cc. You can customize this summary. It will automatically update as commits are pushed.