Conversation
The Aspire extension always requested the "latest" image tag. Docker treats "latest" as an ordinary tag rather than a moving reference resolved on each run, so a host that had already pulled it kept running the image from that first pull. Upgrading the NuGet package therefore left the container on whatever emulator build the host happened to have, which is not necessarily the one the new package expects. The tag is now derived from the package's own informational version, so upgrading the package requests a tag the host does not have yet and the pull brings down the matching emulator. Deriving it from the assembly rather than hardcoding a literal means a release bumps only the csproj version; ImageTag_MatchesPackageVersion asserts the derived tag against the version in the csproj so the two cannot drift apart. The demo app host overrides the tag back to "latest": it tracks the code in the working tree rather than a published release, so the pinned tag does not exist in the registry until the release is tagged. Also prepares the 1.0.0-beta.4 release by bumping both package versions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
paulirwin
marked this pull request as ready for review
September 1, 2026 16:29
paulirwin
enabled auto-merge (squash)
September 1, 2026 16:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #83, and prepares the 1.0.0-beta.4 release.
The problem
The Aspire extension always requested the
latestimage tag. Docker treatslatestas an ordinary tag rather than a moving reference resolved on each run, so a host that had already pulled it kept running the image from that first pull. Upgrading the NuGet package left the container on whatever emulator build the host happened to have — not necessarily the one the new package expects.The fix
The image tag is now derived from the package's own informational version, so upgrading the package requests a tag the host does not have yet and the pull brings down the matching emulator.
Deriving it from the assembly rather than hardcoding a literal means a release bumps only the csproj
<Version>, with no second place to remember to edit.ImageTag_MatchesPackageVersionreads the version straight out of the csproj and asserts the derived tag against it, so the two cannot drift apart. (It deliberately does not compare the derivation against the assembly attribute it is derived from — that would pass no matter what the release version was.)The tag lines up with what the release actually publishes: the Docker workflow tags images via
type=semver,pattern={{version}}, sov1.0.0-beta.4publishes the image tag1.0.0-beta.4.Demo app host
AzureSearchEmulator.Aspire.DemoAppHostoverrides the tag back tolatest. It tracks the code in the working tree rather than a published release, so the pinned tag does not exist in the registry until the release is tagged.Version bump
Both
AzureSearchEmulatorandAzureSearchEmulator.Aspirego to1.0.0-beta.4.Verification
dotnet build AzureSearchEmulator.sln— clean, 0 warnings (the Aspire project builds withTreatWarningsAsErrors).dotnet test AzureSearchEmulator.sln— 1200 passed / 0 failed (7 Aspire, 973 unit, 220 integration).1.0.0-beta.4, rather than relying on the self-referential assertion.🤖 Generated with Claude Code