[deps-release-notes] awf — upstream release action items

[github-actions]

Rolling upstream release action items — awf

This is the single canonical tracking issue for action items arising from new releases of the awf dependency. The dependency version updater workflow appends a new comment to this issue for each version bump, so the most recent activity lives in the comments below.

The companion version-bump PR for the first recorded range is titled chore(deps): update AWF_VERSION to 0.28.26.

awf 0.27.32 → 0.28.26

Releases analyzed

• v0.27.33
• v0.27.34
• v0.27.35
• v0.27.36
• v0.27.37
• v0.27.38
• v0.27.39
• v0.27.41
• v0.27.42
• v0.27.43
• v0.27.44
• v0.28.0
• v0.28.1 ... v0.28.26 (37 releases total in range)

Breaking changes

• None identified. Upstream's v0.28.5 notes explicitly state "There are no breaking changes for existing awf CLI users" for the security-hardening changes below, and no other release in this range documents a removed/renamed flag, changed config schema, or removed egress/safe-output surface.

Security fixes

• Stricter allowWrite filesystem-boundary enforcement (v0.28.5, PR #7634) — AWF now more strictly enforces that sandboxed agents can only write within explicitly allowed paths. Upstream's own upgrade notes ask consumers relying on allowWrite scoping to confirm existing allowlists still cover intended write paths. ado-aw should double-check any mounts it passes with write access (e.g. the ado-proxy -v "${AZ_WRAPPER_DIR}:/var/lib/ado-proxy:rw" mount in agentic_pipeline.rs) still work under the tightened enforcement.
• CLI artifact redirects routed through scoped Squid egress (v0.28.5, PR #7635) — closes a bypass where CLI artifact download redirects could skip the domain-allowlist egress path. No action needed beyond the version bump; purely upstream-side hardening.

Notable features for ado-aw to adopt

• --api-proxy-ca-cert <path> (v0.28.10, PR #7816) — lets the AWF api-proxy sidecar trust an additional CA certificate for upstream TLS verification. Could be useful if ado-aw ever needs to route through a corporate TLS-inspecting proxy for the Copilot/model API traffic.
• --network-subnet <cidr> (v0.28.16, PR #8398) — relocates the awf-net Docker network off its default 172.30.0.0/24 subnet to avoid collisions with host/cluster networks. Worth surfacing as a compiler-level escape hatch if ADO-hosted agent pools ever collide with that default range.
• --reflect (v0.28.13) — starts AWF, queries the API proxy's /reflect endpoint, and prints its JSON response; a lightweight diagnostic mode that could help ado-aw audit/trace verify API-proxy model routing without a full agent run.
• GitHub REST/GraphQL API point budgets (v0.28.26, PR #8978) — adds --max-github-api-points-rest / --max-github-api-points-graphql budget controls to the api-proxy. Could let ado-aw cap GitHub API consumption per Agent job run, complementing its existing tool/network allow-listing model.

Deprecations

• None identified in this range.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• index.crates.io

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "index.crates.io"

See Network Configuration for more information.

Generated by Dependency Version Updater · auto · 175.6 AIC · ⌖ 6.11 AIC · ⊞ 14.3K · ◷

[github-actions]

awf 0.27.32 → 0.28.27

Releases analyzed

• v0.27.33
• v0.27.34
• v0.27.35
• v0.27.36
• v0.27.37
• v0.27.38
• v0.27.39
• v0.27.41
• v0.27.42
• v0.27.43
• v0.27.44
• v0.28.0 ... v0.28.26 (as previously analyzed in the comment above)
• v0.28.27 (new since the last recorded bump)

Breaking changes

• None identified. Same conclusion as the prior comment; v0.28.27 adds no new breaking changes.

Security fixes

• No new security fixes since the prior comment. (The allowWrite filesystem-boundary enforcement and Squid egress routing fixes from v0.28.5 remain the notable security items in this overall range — see the comment above.)

Notable features for ado-aw to adopt

• No new notable features in v0.28.27 itself (documentation clarification + internal test/CI changes only). The previously-noted --api-proxy-ca-cert, --network-subnet, --reflect, and GitHub REST/GraphQL API point budget features (through v0.28.26) remain open adoption candidates — see the comment above.

Deprecations

• None identified in v0.28.27.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• index.crates.io

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "index.crates.io"

See Network Configuration for more information.

Generated by Dependency Version Updater · auto · 273.7 AIC · ⌖ 6.6 AIC · ⊞ 14.3K · ◷