fix: pydantic-sqlalchemy model mismatch

[orhanrauf]

Summary by cubic

Fixes a Pydantic–SQLAlchemy mismatch in the Auth0 auth flow by using the UserUpdate schema to update last_active_at. Prevents validation errors and safely updates the timestamp during authentication.

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="backend/airweave/api/deps.py">

<violation number="1" location="backend/airweave/api/deps.py:56">
UserUpdate ignores last_active_at because the schema lacks that field, so update_user_no_auth never persists the timestamp change.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[cubic-dev-ai]

UserUpdate ignores last_active_at because the schema lacks that field, so update_user_no_auth never persists the timestamp change.

Prompt for AI agents

Address the following comment on backend/airweave/api/deps.py at line 56:

<comment>UserUpdate ignores last_active_at because the schema lacks that field, so update_user_no_auth never persists the timestamp change.</comment>

<file context>
@@ -51,8 +51,10 @@ async def _authenticate_auth0_user(
-    user = await crud.user.update_user_no_auth(db, id=user.id, obj_in=user)
+    from airweave.schemas.user import UserUpdate
+
+    user_update = UserUpdate(last_active_at=datetime.utcnow())
+    user = await crud.user.update_user_no_auth(db, id=user.id, obj_in=user_update)
 
</file context>