13.2 upgrade notes
Aspire.Hosting.Netlify is now built against Aspire 13.2.4 (the latest stable
release in the 13.x line).
What changed
Section titled “What changed”- All Aspire packages are pinned to 13.2.4 in
Directory.Packages.props. - The library and AppHosts use the new
Aspire Type System
attributes so a TypeScript AppHost gets a generated
publishAsNetlifySite(...)surface. See Multi-language. - A directory-only
PublishAsNetlifySite("dist", authToken)overload is now available alongside the canonicalNetlifyDeployOptionsoverload. - The repo’s framework demos moved from
src/<framework>/tosamples/<framework>/. The AppHost was renamed fromNetlify.AppHosttoAllFrameworks.AppHostto reflect what it actually demonstrates. A newQuickstart.AppHostshowcases the directory-only overload. - NuGet.org publishing now uses OIDC Trusted Publishing;
no
NUGET_API_KEYsecret is required.
Behaviour changes (intentional)
Section titled “Behaviour changes (intentional)”| Before | After | Why |
|---|---|---|
NETLIFY_AUTH_TOKEN env var clobbered any explicit authToken parameter. | The parameter wins. The pipeline emits a warning when both are set with different values. | The previous behaviour silently overrode user intent. |
NetlifyDeployOptions.CreateSite = "name" emitted --create-site only — without the supplied name. | --create-site <name> is emitted. | The previous behaviour silently dropped the user-supplied site name. |
If ntl was not initially on PATH, the install step succeeded but the deploy step still failed because the inherited PATH was stale. | After install, the npm-global bin directory is prepended to the current process’s PATH. The deploy step re-resolves the ntl binary. | Restores the documented “auto-install” workflow. |
Package changes
Section titled “Package changes”Aspire.Hosting.AppHostis obsolete in 13.2 and is no longer referenced by AppHost projects. AppHosts only need theAspire.AppHost.SdkSDK and anAspire.Hosting.JavaScriptpackage reference.
Migrating your AppHost
Section titled “Migrating your AppHost”If you upgraded from an earlier 13.x release of this integration, no code changes are required. Run:
aspire updatedotnet restoreIf you want to take advantage of the directory-only overload:
.PublishAsNetlifySite(new NetlifyDeployOptions { Dir = "dist", NoBuild = true }).PublishAsNetlifySite("dist")