Releases

The tagged coordinated AppSurface release represented by this documentation tree.

Coordinated AppSurface release 0.1.0, tagged on 2026-06-27.

Coordinated AppSurface release 0.2.0-preview.1, tagged on 2026-06-28.

Coordinated AppSurface release 0.2.0-preview.10, prepared on 2026-09-28 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.11, prepared on 2026-09-29 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.12, prepared on 2026-10-02 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.13, prepared on 2026-10-04 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.14, prepared on 2026-10-15 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.2, tagged on 2026-07-02.

Coordinated AppSurface release 0.2.0-preview.3, tagged on 2026-07-17.

Coordinated AppSurface release 0.2.0-preview.4, tagged on 2026-07-18.

Coordinated AppSurface release 0.2.0-preview.5, tagged on 2026-07-31.

Coordinated AppSurface release 0.2.0-preview.6, prepared on 2026-08-11 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.7, prepared on 2026-08-15 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.8, prepared on 2026-08-22 for maintainer review.

Coordinated AppSurface release 0.2.0-preview.9, prepared on 2026-09-27 for maintainer review.

Start with the public release hub, then drill into the current v0.2.0 preview, the canonical v0.1.0 archive, unreleased proof, changelog, and upgrade policy.

Maintainer guide for frozen tree-local coordinated package release pointers.

Living proof artifact for the next coordinated AppSurface release. This page is intentionally provisional until a version is tagged.

Compact ledger for coordinated AppSurface releases across packages, CLI tooling, examples, and docs-facing behavior.

Stability and migration contract for AppSurface before the first tagged release.

Maintainer workflow for turning the unreleased proof artifact into a consumer-led tagged release note.

The [Durable worker quickstart](../../start-here/durable-worker.md) introduces the `ForgeTrust.AppSurface.Durable.Templates` package and `appsurface-durable-worker` template for hosts that activate Work through an authenticated ASP.NET Core route. It generates a typed Work definition, passive PostgreSQL composition, distinct health endpoints, telemetry and standalone tests. The disposable first-Work proof exercises authorization, terminal completion, readiness and exported activity against restricted PostgreSQL roles using the [canonical packaged role recipe](../../Durable/ForgeTrust.AppSurface.Durable.PostgreSql/README.md).

`AspireStartupContext` now anchors default repository discovery at `builder.AppHostDirectory` and uses the nearest `.git` directory or file, including linked-worktree markers. Relative explicit `applicationRoot` values that were previously accepted now fail validation; supply a nonblank fully qualified path when constructing a context directly. When no root can be discovered, repository-path requests now fail with a helpful error instead of returning a silent relative path, while path-free profile and factory use remains available. Follow the [canonical repository-relative assets guide](../../Aspire/ForgeTrust.AppSurface.Aspire/README.md#repository-relative-assets) for asset checks and recovery. This behavior change is covered by the [pre-1.0 upgrade policy](../upgrade-policy.md).

The approved `ForgeTrust.AppSurface.Evidence.Readiness` package provides a BCL-only, deadline-bounded HTTP status probe for ordinary tests. Its typed Aspire fixture composes the existing profile builder, native resource health, explicit endpoint selection, and the HTTP condition under one cooperative startup budget. The Evidence.Aspire adapter adds that condition to an explicitly registered EvidenceHost resource while retaining the existing application lease as its sole owner.

The [Aspire integration](../../Aspire/ForgeTrust.AppSurface.Aspire/README.md#dependency-security) now requires MessagePack **2.5.303**, fixing [Dependabot alert #14](https://github.com/forge-trust/AppSurface/security/dependabot/14) and [GHSA-qhrr-8q5h-9q3h](https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-qhrr-8q5h-9q3h). Malformed nested containers are rejected before they can reuse trailing bytes to justify excessive allocations during object deserialization. The supported Aspire **13.4.4** baseline is unchanged; retain the MessagePack security floor when updating Aspire.

adds names-only environment candidate plans for typed native keys, strict string keys, and direct composition paths. The inspector shares the host's frozen mapping snapshot and performs no source reads or value resolution. See the [logical-key guide](../../guides/config-logical-keys.md#environment-candidate-inspection) and [packed consumer proof](https://github.com/forge-trust/AppSurface/blob/main/tests/config-package-consumer/README.md).

[ForgeTrust.AppSurface.Durable.CloudTasks](../../Durable/ForgeTrust.AppSurface.Durable.CloudTasks/README.md) package submits a caller-named empty wake to an existing Durable external-activation host using an explicit creator token source and worker OIDC target. Closed receipts distinguish acceptance, name conflict, definitive rejection, and uncertain outcomes; an uncertain result keeps recovery application-owned. The official SDK transport is bounded and has no application/GAX retries. Its local TLS fixtures observe two streams/one acceptance for one `REFUSED_STREAM` followed by success, four streams/zero acceptances for repeated refusal, four streams/zero acceptances for GOAWAY last-stream-id zero, and one accepted request with a lost response classified `Indeterminate/ASCT305`. These fixture results were observed with .NET SDK 10.0.402 and .NET runtime 10.0.13, and separately with .NET runtime 10.0.2. See the [canonical activation reference](../../Durable/cloudtasks-activation.md) and [local package proof](../../Durable/ForgeTrust.AppSurface.Durable.CloudTasks/README.md#local-proof). Packed GCP and neutral-consumer isolation remain release gates; local fixtures do not prove Google-issued identity, live IAM, or real task delivery.

This is the initial versioned baseline for projects created by `appsurface-durable-worker`. It records the exact generated file inventory and the manual review needed when a later template release changes that shape. There is no earlier template shape to migrate from. The v1 inventory is the predecessor for every later before/after guide.

This change fixes literal `--test-argument` forwarding and adds AppSurface-owned VSTest hang diagnostics to `coverage run` and the first-party Evidence coverage producer. It affects the [AppSurface CLI](../Cli/ForgeTrust.AppSurface.Cli/README.md#appsurface-coverage-run) and its private [Evidence coverage engine](../Evidence/ForgeTrust.AppSurface.Evidence.Coverage/README.md). It applies to the supported VSTest collector and explicit MSBuild drivers; Microsoft Testing Platform is outside this behavior.