Release Notes Action Items for awf 0.27.9 → 0.27.15
This issue summarizes upstream release notes for the awf dependency between the previously pinned version (0.27.9) and the new pinned version (0.27.15), highlighting items that may need follow-up in ado-aw.
The companion version-bump PR is titled chore(deps): update AWF_VERSION to 0.27.15.
Releases analyzed
Note: v0.27.14 does not appear in the upstream releases list and was likely a retracted/deleted release. Its changes are included in v0.27.15's changelog.
Security fixes
- June 2026 safe dependency refresh:
Apply safe dependency updates for June 2026 security refresh in v0.27.12 — AWF's transitive dependencies were refreshed for security. Also includes Update transitive linkify-it to 5.0.1 in lockfile. No specific CVE disclosed in release notes, but ado-aw maintainers should verify whether any of the updated deps overlap with ado-aw's own dependency tree.
Notable features for ado-aw to adopt
-
Portable self-hosted runner doctor agent (v0.27.11): Add portable self-hosted runner doctor agent — AWF now ships a doctor agent for diagnosing self-hosted runner issues (docs added in the same release: docs: add AWF failure diagnosis guide (Self-Hosted Runner Doctor)). ado-aw could consider surfacing a link to this guide in error messages or documentation when AWF startup failures are detected.
-
429 instead of 403 when max turns exceeded (v0.27.13): fix: return 429 instead of 403 when max turns exceeded — AWF now returns HTTP 429 (Too Many Requests) rather than 403 (Forbidden) when the agent's maxRuns limit is hit. If ado-aw's audit or Stage 3 execution code parses AWF HTTP status codes to distinguish "limit reached" from "auth failure", this behavior change should be reflected.
-
Only inference calls count against maxRuns (v0.27.13): fix: only count inference calls against maxRuns limit — Previously, non-inference API calls (e.g. tool calls, other requests) could count against the maxRuns cap. This fix may allow agents to perform more non-inference work within the same limit. ado-aw maintainers may want to review whether the maxRuns constant or documentation needs updating to reflect this corrected semantics.
-
Network isolation deadlock fix (v0.27.11): fix(network-isolation): break topology-attach ordering deadlock starving cli-proxy health gate — Fixed a deadlock in AWF's network topology setup that could cause the CLI proxy health gate to starve. This was a reliability bug; after upgrading, intermittent pipeline failures related to AWF startup should be reduced.
This issue was opened automatically by the dependency version updater workflow.
Generated by Dependency Version Updater · 376.4 AIC · ⌖ 37.9 AIC · ⊞ 40.1K · ◷
Release Notes Action Items for
awf0.27.9→0.27.15This issue summarizes upstream release notes for the
awfdependency between the previously pinned version (0.27.9) and the new pinned version (0.27.15), highlighting items that may need follow-up in ado-aw.The companion version-bump PR is titled
chore(deps): update AWF_VERSION to 0.27.15.Releases analyzed
Security fixes
Apply safe dependency updates for June 2026 security refreshin v0.27.12 — AWF's transitive dependencies were refreshed for security. Also includesUpdate transitive linkify-it to 5.0.1 in lockfile. No specific CVE disclosed in release notes, but ado-aw maintainers should verify whether any of the updated deps overlap with ado-aw's own dependency tree.Notable features for ado-aw to adopt
Portable self-hosted runner doctor agent (v0.27.11):
Add portable self-hosted runner doctor agent— AWF now ships a doctor agent for diagnosing self-hosted runner issues (docs added in the same release:docs: add AWF failure diagnosis guide (Self-Hosted Runner Doctor)). ado-aw could consider surfacing a link to this guide in error messages or documentation when AWF startup failures are detected.429 instead of 403 when max turns exceeded (v0.27.13):
fix: return 429 instead of 403 when max turns exceeded— AWF now returns HTTP 429 (Too Many Requests) rather than 403 (Forbidden) when the agent'smaxRunslimit is hit. If ado-aw's audit or Stage 3 execution code parses AWF HTTP status codes to distinguish "limit reached" from "auth failure", this behavior change should be reflected.Only inference calls count against maxRuns (v0.27.13):
fix: only count inference calls against maxRuns limit— Previously, non-inference API calls (e.g. tool calls, other requests) could count against themaxRunscap. This fix may allow agents to perform more non-inference work within the same limit. ado-aw maintainers may want to review whether themaxRunsconstant or documentation needs updating to reflect this corrected semantics.Network isolation deadlock fix (v0.27.11):
fix(network-isolation): break topology-attach ordering deadlock starving cli-proxy health gate— Fixed a deadlock in AWF's network topology setup that could cause the CLI proxy health gate to starve. This was a reliability bug; after upgrading, intermittent pipeline failures related to AWF startup should be reduced.This issue was opened automatically by the dependency version updater workflow.