Migrate Aspire apps from GitHub Models
Questi contenuti non sono ancora disponibili nella tua lingua.
The GitHub Models playground, model catalog, inference API, and bring your own key (BYOK) capabilities are no longer available. Existing apps that use the Aspire GitHub Models integration can’t send inference requests to the retired service.
Migrate to Microsoft Foundry
Section titled “Migrate to Microsoft Foundry”Microsoft Foundry provides a broad model catalog and supports both cloud-hosted deployments and local development. To migrate:
- Remove the
Aspire.Hosting.GitHub.Modelspackage from your AppHost and remove GitHub Models resources, API key parameters, andGITHUB_TOKENconfiguration. - Follow the Microsoft Foundry hosting integration guide to add a Foundry resource and model deployment. For local development, you can configure the resource to run with Foundry Local.
- Reference the Foundry deployment from each consuming app that needs model access.
- Follow Connect to Microsoft Foundry to update client configuration and environment-variable handling. Don’t reuse retired GitHub Models endpoints, tokens, or model identifiers.
Aspire 13.5 historical reference
Section titled “Aspire 13.5 historical reference”The Aspire.Hosting.GitHub.Models source, tests, and playground sample were removed from the Aspire repository in Aspire 13.6. The final 13.5.x package remains published on NuGet for apps that already reference it, but it’s hidden from aspire add and isn’t rebuilt or serviced going forward.
The following articles document the final Aspire 13.5 integration surface for migration and historical reference. Their examples don’t restore access to the retired GitHub Models service:
Aspire