Upstream update: dotnet-aspire

[github-actions]

Automation detected pending upstream changes for dotnet-aspire.

• Issue key: dotnet-aspire
• Affected skills: dotnet-aspire
• Pending upstream watches: 2

Pending upstream sources:

• aspire-docs | http_document | aspire.dev/ documentation
  • Source: https://aspire.dev/
  • Current value: "kTNOQaIYVRQO/uvShCV9zDtep861o8Qr7hVLxzb0j2I="
  • Detail: Aspire — Your stack, streamlined | ETag "kTNOQaIYVRQO/uvShCV9zDtep861o8Qr7hVLxzb0j2I="
• aspire-release | github_release | dotnet/aspire release
  • Source: https://github.com/dotnet/aspire/releases/tag/v13.1.3
  • Current value: v13.1.3
  • Published at: 2026-03-19T20:13:58Z
  • Detail: v13.1.3 (2026-03-19T20:13:58Z)

Why this matters:

• Review the linked skills when https://aspire.dev/ changes.
• Review the linked skills when dotnet/aspire ships a new release.

Suggested follow-up:

• Review the upstream release notes or documentation diff
• Update the affected files under skills/
• Update README.md if framework coverage or guidance changed
• Close this issue after the catalog has been refreshed

[github-actions]

Automation detected another upstream change for this watch.

• Watch id: aspire-docs
• Previous value: "ZJs6BvVxvCdmhy7+5xFEjE7rNto0awpcVW9/AxDqLj4="
• Current value: "NImqlziy4Dzs9nqs9N1uYFQaIvi4xed6bQT+NsA1ALo="
• Source: https://aspire.dev/

[KSemenenko]

Closed as part of the upstream-watch cleanup in #471. The watcher now groups related updates into one issue per skill set, paginates the full issue set for dedup, and the upstream baseline was resynced so these backlogged issues do not reopen immediately.