Menu
Update the Aspire version in the repository to the latest nightly build.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Guides authoring and reviewing CommunityToolkit Aspire.Hosting integration APIs. Classifies integration archetypes, then applies self-contained best practices for naming, resource shape, run/publish/deploy behavior, eventing, connection properties, security, endpoint semantics, polyglot exports, READMEs, and tests.
{what this skill teaches agents}
Team initialization flow (Phase 1 proposal + Phase 2 creation)
User-level AI agents that travel with you across projects
Capture Playwright screenshots and embed them in GitHub PR descriptions
Pre-release validation, npm publish procedures, and post-publish verification
| name | aspire-upgrade |
| description | Update the Aspire version in the repository to the latest nightly build. |
The target version prefix is 13.4.
You are responsible for updating the Aspire version in our repo to the latest nightly build.
You are to use the NuGet feed https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json
Look for the latest nightly version that starts with the target version prefix above. To do this, you will need to use the .NET CLI package search feature with the --prerelease and --exact-match flags (and probably best to specify the feed with --source to avoid confusion with any stable versions from nuget.org). Query for the Aspire.AppHost.Sdk package as it is a dependency of all our AppHost projects and will be the most reliable way to find the correct version string.
Here is an example command to find the latest version:
dotnet package search Aspire.AppHost.Sdk --prerelease --exact-match --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9/nuget/v3/index.json --format json
Parse the result for the latest version that matches the target version prefix. This will be the version you update to in the next steps.
Directory.Build.propsUpdate the following values in the root Directory.Build.props file:
<AspireMajorVersion>MAJOR_VERSION</AspireMajorVersion>
<AspireVersion>$(AspireMajorVersion).MINOR_VERSION.PATCH_VERSION-PREVIEW_VERSION</AspireVersion>
<AspirePreviewSuffix></AspirePreviewSuffix>
Where MAJOR_VERSION, MINOR_VERSION, PATCH_VERSION, and PREVIEW_VERSION are the respective parts of the version you found.
When using a nightly build, we want to blank out the AspirePreviewSuffix to avoid confusion with the actual preview versions.
Search the entire repository for all .csproj files whose <Project Sdk="..."> attribute references Aspire.AppHost.Sdk. There are many of these across tests/, tests-app-hosts/, and examples/.
Each one must be updated to the full version string:
<Project Sdk="Aspire.AppHost.Sdk/MAJOR_VERSION.MINOR_VERSION.PATCH_VERSION-PREVIEW_VERSION">
We cannot use a MSBuild variable in the Project SDK attribute, so you must hardcode the version in every file.
Use a command like grep -rl "Aspire.AppHost.Sdk" --include="*.csproj" to find all files that need updating.
aspire.config.json filesSearch the entire repository for all aspire.config.json files (typically under examples/ in directories ending with .AppHost.TypeScript). Each file has an sdk.version field that must be updated to the new version.
The sdk.version value should be the full version string (e.g., 13.4.0-preview.1.25280.1).
Use a command like find . -name "aspire.config.json" to locate all files, then update the "version" value inside the "sdk" object in each one.
Run dotnet restore at the repository root to verify the new version resolves correctly. Fix any errors before proceeding.
After all changes are made and validated, create a pull request with the title "Update Aspire version to X.Y.Z" where X.Y.Z is the full version you updated to.