You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .kiro/steering/docs.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,18 +376,22 @@ table_order:
376
376
377
377
### Support Policy Consolidation
378
378
379
-
The `framework_groups` configuration consolidates support policy rows by framework. Repositories in the same group are combined into a single row using the framework name (e.g., "PyTorch").
379
+
The `framework_groups` configuration consolidates support policy rows by framework. The generation follows a 3-step flow:
380
380
381
-
**Version Display:**
381
+
**Validation (at load time):**`load_repository_images` validates that images sharing the same full version within a single repository have identical GA/EOP dates. Raises `ValueError` if not (this is a data bug).
382
382
383
-
- Images with the same major.minor version (e.g., `2.6.0` and `2.6.1`) are consolidated into a single row displayed as `2.6` if they have identical GA/EOP dates
384
-
- If patch versions have different GA/EOP dates, each is displayed separately with full version (e.g., `2.6.0`, `2.6.1`) and a warning is logged
383
+
**Step 1 — Group by full version:** All images in a framework group are grouped by full version (e.g., `2.6.0`), deduplicated per repository (one representative image per repo since intra-repo consistency is guaranteed).
384
+
385
+
**Step 2 — Cross-repo agreement check:** For each full version, check if all repositories agree on GA/EOP dates:
386
+
387
+
- If all repositories agree → one entry using the framework group name (e.g., "PyTorch")
388
+
- If repositories disagree → warning logged, each repository gets its own row using its individual display name (e.g., "PyTorch Inference")
389
+
390
+
**Step 3 — Major.minor collapse:** Non-split entries are grouped by major.minor. If all full versions within a major.minor share the same dates, they collapse into a single row displayed as the major.minor (e.g., `2.6`). Collapse is skipped for any major.minor that has split (per-repo) rows.
385
391
386
392
**Requirements:**
387
393
388
-
- All repositories in a group that have a given full version (X.Y.Z) must have identical GA/EOP dates
389
394
- Missing versions in some repositories are allowed (only present repos are consolidated)
390
-
- A `ValueError` is raised if dates differ within a group for the same full version
391
395
392
396
To add a new framework group, add an entry to `framework_groups` with the framework name as key and list of repositories as value.
0 commit comments