Repository navigation
fix: diagnose unsupported stored configuration with safe recovery - #642
Conversation
|
To preview the documentation for this pull request, visit the following URL:
|
Copilot approval · Human review neededStatus: A protected workflow, policy, or trust-boundary file changed. Technical evidenceRevision: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #642 +/- ##
===========================================
+ Coverage 90.94% 94.11% +3.16%
===========================================
Files 135 950 +815
Lines 6251 30588 +24337
Branches 1338 8980 +7642
===========================================
+ Hits 5685 28788 +23103
- Misses 172 704 +532
- Partials 394 1096 +702
🚀 New features to boost your workflow:
|
Bugbot: review complete
|
|
/copilot sync-branch --from develop |
…supported-pr-configuration-schemas
Branch synchronized
6 verification checks passed. |
|
/copilot recheck |
|
/copilot sync-branch --from develop --no-agent |
…supported-pr-configuration-schemas
Branch synchronized
6 verification checks passed. |
|
/copilot recheck |
|
/copilot sync-branch --from develop |
…supported-pr-configuration-schemas
Branch synchronized
6 verification checks passed. |
|
/copilot recheck |
Unsupported stored Copilot configuration now fails as a nonretryable
configuration.invaliderror with its correlation reference preserved and actionable recovery guidance in the failure annotation and Job Summary. Strict schema validation remains in place, while absent and current-schema configurations retain their existing behavior.What changed
Validation
pnpm run test:coverage: 687 suites passed; 11,196 tests passed; 35 skipped. Coverage budgets and the setup acceptance validator passed; overall coverage was 97.77% lines and 94.24% branches, with 100% coverage for the configuration reader.Review notes
Closes #635