Handle incomplete Extension Gallery latest responses

[Dmitriy Vasyura (dmitrivMS)]

Summary

• treat latest-version responses without asset-file metadata as incomplete
• use the existing Extension Gallery query fallback without logging a TypeError
• make raw asset lookup tolerate omitted files
• cover the managed-feed response shape with a focused service test

Testing

• npm run transpile-client
• scripts\test.bat --run src\vs\platform\extensionManagement\test\common\extensionGalleryService.test.ts (31 passing)

Fixes #330526

[Copilot]

Pull request overview

Handles incomplete Extension Gallery responses by falling back cleanly to the query API.

Changes:

• Makes raw extension file metadata optional and asset lookup null-safe.
• Detects missing metadata before processing latest versions.
• Adds focused fallback and error-logging coverage.

Show a summary per file

File	Description
extensionGalleryService.ts	Handles omitted version files and triggers query fallback.
extensionGalleryService.test.ts	Verifies fallback occurs without logging errors.

Review details

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Balanced

[Copilot]

One or more custom setup steps configured for this repository failed during this Copilot code review run:

Download Electron and Playwright

Setup steps run before each review. If the review above is missing context, or no review was posted at all, the failing step above may be the cause. See the workflow run for failure details, fix your setup steps configuration, and re-request a review.

Note

You can configure setup steps for Copilot code review separately from Copilot cloud agent with a copilot-code-review.yml file. Read the docs for details.