feat: track app version on each review event #5

Merged
rcsheets merged 1 commit from feat/track-app-version into main 2026-03-20 21:32:15 +00:00
Owner

Stores the pr-reviewer version that processed each event in the
database. Cheap to store, useful for debugging behavior differences
across deployments.

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

Stores the pr-reviewer version that processed each event in the database. Cheap to store, useful for debugging behavior differences across deployments. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Stores the pr-reviewer version that processed each event in the
database. Cheap to store, useful for debugging behavior differences
across deployments.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator

Automated review by pr-reviewer v0.8.0 | Safety Check | anthropic | tracking id r-bdbc49-90a789

Status: Completed


Looking at this pull request, I can see it's adding version tracking to review events by:

  1. Adding an app_version field to the ReviewEvent class
  2. Adding the column to the database schema and migration
  3. Updating all database queries to include the new field
  4. Passing VERSION to event creation calls

The changes look straightforward and consistent. However, I notice that VERSION is being referenced in main.py but I don't see where it's defined or imported in the diff. This could cause a NameError at runtime if VERSION isn't properly imported or defined.

The database migration looks safe with ADD COLUMN IF NOT EXISTS, and all the SQL queries have been updated consistently to handle the new column.

Verdict: Flag - The VERSION variable appears to be undefined in main.py.

*Automated review by [pr-reviewer](https://git.brooktrails.org/brooktrails/pr-reviewer) v0.8.0 | Safety Check | anthropic | tracking id `r-bdbc49-90a789`* **Status:** ✅ Completed --- Looking at this pull request, I can see it's adding version tracking to review events by: 1. Adding an `app_version` field to the `ReviewEvent` class 2. Adding the column to the database schema and migration 3. Updating all database queries to include the new field 4. Passing `VERSION` to event creation calls The changes look straightforward and consistent. However, I notice that `VERSION` is being referenced in `main.py` but I don't see where it's defined or imported in the diff. This could cause a `NameError` at runtime if `VERSION` isn't properly imported or defined. The database migration looks safe with `ADD COLUMN IF NOT EXISTS`, and all the SQL queries have been updated consistently to handle the new column. **Verdict: Flag** - The `VERSION` variable appears to be undefined in `main.py`.
rcsheets deleted branch feat/track-app-version 2026-03-20 21:32:15 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
brooktrails/pr-reviewer!5
No description provided.