Skip to content

fix(compat): set last_updated when storing a task in v0.3 format - #1372

Merged
Iwaniukooo11 merged 1 commit into
a2aproject:mainfrom
ConnorMoss02:fix/v03-model-last-updated
Oct 23, 2026
Merged

Iwaniukooo11 merged 1 commit into
a2aproject:mainfrom
ConnorMoss02:fix/v03-model-last-updated

Conversation

@ConnorMoss02

Copy link
Copy Markdown
Contributor

Problem

core_to_compat_task_model left last_updated unset, so in zero-downtime migration mode ListTasks with status_timestamp_after returned nothing.

Fix

Set it from status.timestamp, as the v1.0 path in DatabaseTaskStore does.

Tests

test_task_db_conversion_sets_last_updated fails on main. 2305 passed.

Fixes #1371

@ConnorMoss02
ConnorMoss02 requested a review from a team as a code owner October 23, 2026 04:43
@github-actions

Copy link
Copy Markdown

🧪 Code Coverage (vs main)

⬇️ Download Full Report

No coverage changes.

Generated by coverage-comment.yml

@Iwaniukooo11 Iwaniukooo11 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Iwaniukooo11
Iwaniukooo11 merged commit 30b6d50 into a2aproject:main Oct 23, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Zero-downtime migration mode stores tasks without last_updated

2 participants