Fix changeset_repository.py get_for_plan to preserve per-changeset granularity #8194

Merged

HAL9000 merged 1 commits from issue-7502-fix-get-for-plan into master

2026-06-02 11:17:01 +00:00

Author	SHA1	Message	Date
HAL9000	652d807360	fix(changeset_repository): preserve per-changeset granularity in get_for_plan CI / lint (pull_request) Successful in 46s Details CI / push-validation (pull_request) Successful in 30s Details CI / helm (pull_request) Successful in 39s Details CI / build (pull_request) Successful in 43s Details CI / typecheck (pull_request) Successful in 1m2s Details CI / quality (pull_request) Successful in 1m21s Details CI / security (pull_request) Successful in 1m27s Details CI / unit_tests (pull_request) Successful in 6m10s Details CI / docker (pull_request) Successful in 1m44s Details CI / integration_tests (pull_request) Successful in 10m5s Details CI / coverage (pull_request) Successful in 8m36s Details CI / status-check (pull_request) Successful in 3s Details Previously get_for_plan() collapsed all ChangeEntry rows from a plan into a single SpecChangeSet, losing the ability to distinguish between separate changeset scopes. This restores per-changeset grouping by querying raw DB rows and partitioning them by changeset_id before constructing individual SpecChangeSet objects.	2026-06-02 06:47:33 -04:00