☎️ Aspire Roadmap - Q1 2026 Update (March 2026) #15662
Pinned
maddymontaquila
announced in
Announcements
Replies: 3 comments 1 reply
-
|
Looks great! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Exciting times ahead! Can't wait to hear "13.3 is our biggest release yet" 😎 |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
For polyglot - have you considered adding PHP to the list? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Aspire Roadmap - Q1 2026 Update (March 2026) ☎️
It's been a few months since our end of year update, and we've finally shipped Aspire 13.2 (March 2026) — our biggest ever release!!! Here's an update on our progress against the original roadmap and some thoughts on what's next.
As always, thank you all for the support, contributions, bug reports, and encouragement. 13.2 was a lot of work, and your patience while we slowed down our ship cadence (so we can speed up in the future!) was greatly appreciated.
🎉 Major Accomplishments
Aspire 13.2 was a massive release with 1,100+ closed issues, focused on three themes: CLI as a first-class agent interface, TypeScript AppHost (preview), and making local development seamless for both developers and AI coding agents. The What's New on aspire.dev has all the details.
The CLI is now purpose-built for AI coding agents — detached mode, structured output, health-check blocking, and telemetry streaming make every command automation-friendly and agent-consumable.
TypeScript AppHost lets you write your entire app model in TypeScript with
createBuilder(), using the same resource/reference/integration concepts as C#. This is a huge step toward making Aspire truly language-agnostic.The VS Code extension received its biggest update yet with a dedicated Activity Bar panel, inline CodeLens with live resource state, gutter decorations, and a Getting Started walkthrough.
Microsoft Foundry replaces Azure AI Foundry with broader support for hosted agents, model deployments, and Foundry Projects directly from the app model.
And, we're excited to share that Homebrew & WinGet packages will be available soon for the Aspire CLI.
We also spent a lot of time in this release working under-the-hood on infra, tests, code review processes, and tech debt, which will help us ship stable, well-tested releases of Aspire to you more often! And - you might notice we have a new home on GitHub 😉
🧑💻 Local Developer Experience
.localhostDNS Supportaspire start/stop/ps)--isolated)aspire resource)aspire doctor)aspire describe)aspire certs)🧪 Testing Experience
aspire waitCommand📊 Dashboard Enhancements
🛠 Tooling
init,update,run,new,do)start,stop,ps,describe,doctor,wait,export)secret,certs,docs,restore)aspire.config.jsonaspire agent)aspire mcp, adds SKILL.md)🌐 Polyglot Support
WASM + WITJSON RPC)WithBun()for JS resources)aspire new)🤖 AI Workflows
WithMcpServerApp Model APIIEmbeddingGeneratorvia Azure AI Inference)aspire agent)☁ Hosting Integrations
Aspire.MongoDB.EntityFrameworkCore)WithPurgeTask)rediss://default in 13.2)🚀 Deployment
Pipeline & CI/CD:
aspire dopipeline system shipped (13.0)📈 By the Numbers
🔮 Looking Ahead
Testing remains our largest gap.
aspire waitis a useful building block for CI scripts, but we still need first-class testing experiences — live dashboard during tests, capture & replay, partial apphost execution, and request mocking. This remains a top priority.Running a subset of Aspire resources continues to be critical for larger projects. Detached mode and
aspire resource start/stopgive you more control, but we want a first-class "run only these resources" experience. Multi-repo support continues to be a popular community ask, especially for enterprise teams with distributed codebases.Dashboard persistence (external storage for telemetry) remains on our radar. The new export/import and telemetry HTTP API are stepping stones, but we know teams want persistent storage for production-like observability.
Debugging in containers is still one of our most requested features. This requires engineering work in both Visual Studio and VS Code to make the experience seamless.
TypeScript AppHost is in preview and we're actively iterating. Expect more integration coverage, better error messages, and performance improvements as we work toward GA. The polyglot export system now covers 30+ integrations and we're expanding to Go, Java, and Rust code generation targets.
Authentication integrations (Entra ID, Keycloak, Easy Auth) remain in progress and are a key focus for upcoming releases.
📚 Resources
Beta Was this translation helpful? Give feedback.
All reactions