chore: Update integration data and GitHub stats (9/8/26)

[aspire-repo-bot]

Automated integration data update — 9/8/26

Generated deterministically by src/frontend/scripts/update-integration-data.ps1 (no agent inference).

What's updated

• src/frontend/src/data/aspire-integrations.json — latest package information
• src/frontend/src/data/github-stats.json — repository statistics
• src/frontend/src/data/samples.json — sample metadata, when changed
• src/frontend/src/assets/samples/ — sample thumbnails, when changed

API reference regeneration

No integration package versions changed in this run — API reference regeneration was skipped.

Review checklist

• Integration data looks reasonable (no suspicious anomalies)
• Package counts and versions updated appropriately
• Official Aspire package icons still use package-specific NuGet icon URLs

[Copilot]

🟡 Changes recommended

The updated integrations dataset still contains tag typos/formatting (e.g., postgressql, o/rm) that break expected search/filter behavior in the integrations gallery.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Automated refresh of the frontend’s generated integration metadata and GitHub repository statistics used by aspire.dev UI pages (e.g., integrations gallery and repo stats displays).

Changes:

• Updated github-stats.json star counts for tracked repositories.
• Updated aspire-integrations.json NuGet download counts (versions unchanged in this run).

File summaries

File	Description
src/frontend/src/data/github-stats.json	Refreshes GitHub repository star counts used for site stats.
src/frontend/src/data/aspire-integrations.json	Refreshes integration download counts used for sorting and display in the integrations gallery.

Review details

Suppressed comments (6)

src/frontend/src/data/aspire-integrations.json:1676

• The tag value "o/rm" includes a slash, which prevents users from finding these integrations by searching for "orm" (tag matching uses substring checks) and is inconsistent with other tag slugs (e.g., "orm" appears elsewhere in this dataset). Consider normalizing this tag to "orm" (and updating other occurrences too).

      "o/rm",

src/frontend/src/data/aspire-integrations.json:1581

• These integrations use the tag value "o/rm" (see nearby tag list), which prevents users from finding them by searching for "orm" (the gallery filter uses substring checks on tag strings). Normalizing to "orm" improves discoverability and keeps tags as simple slugs.

    "downloads": 6045416,

src/frontend/src/data/aspire-integrations.json:1807

• These integrations use the tag value "o/rm" (see nearby tag list), which prevents users from finding them by searching for "orm" (the gallery filter uses substring checks on tag strings). Normalizing to "orm" improves discoverability and keeps tags as simple slugs.

    "downloads": 249799,

src/frontend/src/data/aspire-integrations.json:1833

• These integrations use the tag value "o/rm" (see nearby tag list), which prevents users from finding them by searching for "orm" (the gallery filter uses substring checks on tag strings). Normalizing to "orm" improves discoverability and keeps tags as simple slugs.

    "downloads": 419414,

src/frontend/src/data/aspire-integrations.json:1556

• These integrations use the tag value "o/rm" (see nearby tag list), which prevents users from finding them by searching for "orm" (the gallery filter uses substring checks on tag strings). Normalizing to "orm" improves discoverability and keeps tags as simple slugs.

    "downloads": 236186,

src/frontend/src/data/aspire-integrations.json:1762

• These integrations use the tag value "o/rm" (see nearby tag list), which prevents users from finding them by searching for "orm" (the gallery filter uses substring checks on tag strings). Normalizing to "orm" improves discoverability and keeps tags as simple slugs.

      "npgsql",

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

---

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

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1629. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.