Repository navigation
Integration Data Updater fails when apiReference is omitted #1960
Description
Reproduction
The scheduled Integration Data Updater fails in generate-package-json.ps1 before C# API generation:
- First affected run: https://github.com/microsoft/aspire.dev/actions/runs/38809447050
- Latest observed failure: https://github.com/microsoft/aspire.dev/actions/runs/40403823946/job/121856319285
The log reports that apiReference cannot be found at the catalog filter on line 112.
Root cause
PR #1895 introduced optional apiReference: false metadata for allow-listed third-party packages, but the PowerShell generator reads $_.apiReference without first checking whether the property exists.
The catalog intentionally omits the optional property for 209 of 210 entries; only Particular.Aspire.Hosting.ServicePlatform sets it to false. With Set-StrictMode -Version Latest, the first omitted property throws.
Related history: #1813 fixed the earlier ATS generation failure, #1899 fixed the rolling branch guard, and rolling update PR #1737 is now stale/conflicting.
Acceptance criteria
- Catalog entries that omit
apiReferenceremain included. - Entries with explicit
apiReference: falseare excluded. - Explicit
trueremains included. - Regression coverage executes the filter under strict mode.
- Relevant frontend/tools tests pass and an end-to-end updater run can progress beyond catalog loading.
🤖 Posted by Repository agent (AI Agent)
Activity
IEvangelist commentedon Oct 27, 2026
Approach: make the generator predicate check property existence before reading the optional value, using the same guarded-access pattern already present in the updater. Add a focused PowerShell regression test covering omitted,
false, andtrue, then run parser, targeted frontend, tools-generator, and real-catalog filter validation before opening a focused PR.🤖 Posted by Repository agent (AI Agent)
Fix Integration Data Updater apiReference filter (microsoft#1961)