tidy: aspire — reconcile to 13.4.3 and pin local-dev port band#31
Merged
Conversation
…oints The file-based apphost.cs did not restore under the repo's Central Package Management: dotnet run generates a synthetic apphost.csproj at the repo root that inherits Directory.Packages.props, so the inline #:package versions hit NU1008 and the SDK's implicit Aspire.Hosting.AppHost reference hits NU1009. Opt out via #:property ManagePackageVersionsCentrally=false. Pin Dispatch to 5310/5311 and the Postgres host port to 5390 in apphost.cs; dashboard/OTLP/resource/MCP to 5300-5307 via Properties/launchSettings.json.
erikshafer
force-pushed
the
tidy/aspire-reconcile-and-port-band
branch
from
fa96129 to
7b00b5d
Compare
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
1 participant
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.
First
tidy: aspiresession. Reconciles the drifted Aspire version to a single line and pins CritterCab's local-dev ports so it stops colliding with the other Critter-family projects (crittermart,mmo-reconnect,CritterBids) running on the same machine.What changed
apphost.cs, theaspireskill,README, andCLAUDE(version-of-record only; historical "changed in 13.2" notes left intact on purpose).53xxport band pinned and documented — dashboard/OTLP/resource/MCP5300–5307(newProperties/launchSettings.json); Dispatch5310/5311and Postgres5390(apphost.cs). New Port allocation section in theaspireskill with a cross-project band registry (Mart51xx, MMO52xx, Cab53xx) and a+5per-service slot convention.8284c74): the file-based AppHost did not restore under the repo's Central Package Management.dotnet run apphost.csgenerates a syntheticapphost.csprojat the repo root that inheritsDirectory.Packages.props, so inline#:packageversions hit NU1008 and the SDK's implicitAspire.Hosting.AppHostreference hits NU1009. Fixed with#:property ManagePackageVersionsCentrally=false. This corrects the prompt's "entries are inert" premise.adding-a-service↔aspirecontradiction on AppHost location (repo root, notsrc/AppHost/).Verification
dotnet build apphost.csclean (one pre-existingMessagePackNU1903 warning, transitive).Properties/launchSettings.jsonand applies the first profile by default).aspire run(boots Postgres via Docker) was not run this session — recommend confirming once that the dashboard bindshttps://localhost:5300and Dispatch binds5310/5311.Follow-ups (out of scope, queued in the retro)
Wolverine/Marten/Polecat doc-drift ·
WolverineFx.Grpc/Polecat5.38-vs-6.8 mismatch · buildCritterCab.ServiceDefaults·"CritterBids API"Swagger title typo ·MessagePackNU1903 advisory ·packages.jasperfx.net403 during restore.Prompt:
docs/prompts/aspire-reconcile-and-port-band.md· Retro:docs/retrospectives/aspire-reconcile-and-port-band.md· Null spec-delta (infrastructure/convention, no narrative or workshop amended).