Skip to content

Fill gaps in What's new in Aspire 13.4#1127

Open
maddymontaquila wants to merge 3 commits into
release/13.4from
docs/whats-new-13-4
Open

Fill gaps in What's new in Aspire 13.4#1127
maddymontaquila wants to merge 3 commits into
release/13.4from
docs/whats-new-13-4

Conversation

@maddymontaquila
Copy link
Copy Markdown
Contributor

Audits the existing What's new in Aspire 13.4 draft against the full 13.4 changelog and fills notable user-facing gaps while keeping the existing structure.

What changed

  • New More ways to model your app section covering the new Go (AddGoApp), Blazor WebAssembly (AddBlazorWasmProject/AddBlazorGateway), and Bun (AddBunApp) hosting integrations. The intro promised a broader app model but only covered TypeScript.
  • CLI: deployment commands (aspire publish/aspire deploy) are GA, faster AppHost startup, and automatic .aspire/settings.json -> aspire.config.json migration.
  • App model: persistent executable and project lifetimes (WithPersistentLifetime()/WithSessionLifetime()).
  • Azure: WithAcrPullIdentity and stable Azure Container Apps jobs APIs.
  • Dashboard: structured search + trace duration filtering, and waiting-dependency details.
  • VS Code: Go debugging, multi-AppHost workspaces, AppHost logs viewer, parser-backed detection.
  • Integrations: RabbitMQ default image 4.2 -> 4.3.
  • Breaking changes: expanded the table and migration steps (WithRoute -> WithPath, external endpoints required for routes, Foundry WithComputeEnvironment, PublishAsPackageScript, Keycloak HTTPS).

Validation

  • pnpm build:skip-search succeeds: 12,349 pages built and all internal links valid.

All added APIs and cross-links were verified against existing docs pages.

Audit the 13.4 what's new against the full changelog and add notable user-facing items while keeping the existing structure:

- New 'More ways to model your app' section: Go (AddGoApp), Blazor WebAssembly (AddBlazorWasmProject/AddBlazorGateway), and Bun (AddBunApp) hosting integrations.
- CLI: deployment commands GA, faster startup, and automatic settings.json -> aspire.config.json migration.
- App model: persistent executable and project lifetimes (WithPersistentLifetime/WithSessionLifetime).
- Azure: WithAcrPullIdentity and stable Azure Container Apps jobs APIs.
- Dashboard: structured search/trace duration filtering and waiting-dependency details.
- VS Code: Go debugging, multi-AppHost workspaces, AppHost logs viewer, parser-backed detection.
- Integrations: RabbitMQ default image 4.2 -> 4.3.
- Expanded breaking-changes table and migration steps (WithRoute->WithPath, external endpoints for routes, Foundry WithComputeEnvironment, PublishAsPackageScript, Keycloak HTTPS).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 29, 2026 19:17
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the “What’s new in Aspire 13.4” page to better reflect notable, user-facing additions and breaking changes from the 13.4 changelog, keeping the existing document structure while filling key gaps.

Changes:

  • Adds a new “More ways to model your app” section highlighting new Go, Blazor WebAssembly, and Bun hosting integrations.
  • Expands coverage of CLI, AppHost/app model, Azure, Dashboard, and VS Code extension improvements.
  • Extends the Breaking changes table and migration checklist with additional 13.4 updates.
Show a summary per file
File Description
src/frontend/src/content/docs/whats-new/aspire-13-4.mdx Expands the Aspire 13.4 “What’s new” draft with additional feature highlights and breaking-change migration guidance.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 8

Comment on lines +148 to +149
var api = builder.AddGoApp("api", "./api")
.WithHttpEndpoint(env: "PORT");

const builder = await createBuilder();

const api = await builder.addGoApp('api', './api');

### Blazor WebAssembly hosting

The new `Aspire.Hosting.Blazor` integration models standalone Blazor WebAssembly projects in your AppHost. Use `AddBlazorWasmProject` / `addBlazorWasmProject` to add a Blazor WebAssembly project and `AddBlazorGateway` / `addBlazorGateway` to add a browser-facing gateway that serves the hosted app and routes API calls to your backend resources.
Comment on lines +192 to +195
var blazorApp = builder.AddBlazorWasmProject("app", "../MyBlazorApp/MyBlazorApp.csproj");

var gateway = builder.AddBlazorGateway("gateway")
.WithReference(blazorApp);
Comment on lines +148 to +149
var api = builder.AddGoApp("api", "./api")
.WithHttpEndpoint(env: "PORT");

const builder = await createBuilder();

const api = await builder.addGoApp('api', './api');

### Blazor WebAssembly hosting

The new `Aspire.Hosting.Blazor` integration models standalone Blazor WebAssembly projects in your AppHost. Use `AddBlazorWasmProject` / `addBlazorWasmProject` to add a Blazor WebAssembly project and `AddBlazorGateway` / `addBlazorGateway` to add a browser-facing gateway that serves the hosted app and routes API calls to your backend resources.
Comment on lines +192 to +195
var blazorApp = builder.AddBlazorWasmProject("app", "../MyBlazorApp/MyBlazorApp.csproj");

var gateway = builder.AddBlazorGateway("gateway")
.WithReference(blazorApp);
maddymontaquila and others added 2 commits May 29, 2026 16:07
… flagship emojis

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- **TypeScript AppHost general availability** with stronger startup validation, more complete TypeScript SDK generation, new TypeScript samples, and documentation parity with C# AppHost examples.
- **C# and TypeScript AppHosts are first class and supported** with stronger TypeScript startup validation, more complete SDK generation, new TypeScript samples, and documentation parity with C# AppHost examples.
- **Aspire skills for AI coding agents** with `aspire agent init`, a dedicated deployment skill, and workflow skills distributed through the external [`@microsoft/aspire-skills`](https://www.npmjs.com/package/@microsoft/aspire-skills) npm package.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we are doing an NPM package anymore. For 13.4 we are baking the skills into the CLI but they are still ultimately coming from this repo as part of our build process.

Rephrase as we are now hosting the aspire-skills in the [repo] repo. We integrate the latest skills into new builds of the CLI and in the future we plan to allow for easily updating them even inbetween releases so that we can react quickly when new models ship and we need to fine tune skills.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pinging @IEvangelist for this take on this.

| `aspire-orchestration` | Manages AppHost lifecycle tasks such as start, stop, wait, restart, and recovery from file locks, port conflicts, or orphaned processes. |
| `aspireify` | Wires an AppHost after `aspire init` by scanning the repo, proposing a resource graph, editing the AppHost, adding service defaults, and validating with `aspire start`. |

The skills are distributed through the external [`@microsoft/aspire-skills`](https://www.npmjs.com/package/@microsoft/aspire-skills) npm package, verified with npm provenance and cached locally, so they can be updated independently of the CLI.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think put a call to action here about the fact that we are now starting to automatically evaluate the skill performance with different models and adjusting the skills continuously. But if you see the agents do something in a sub-optimal way or you have any other feedback place open an issue on microsoft/aspire.

Side question: We are going multi-repo here, I wonder what our strategy is going to be around issue management for microsoft/aspire-skills.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants