Release Notes Action Items for awf 0.25.48 → 0.25.65
This issue summarizes upstream release notes for the awf dependency between the previously pinned version (0.25.48) and the new pinned version (0.25.65), highlighting items that may need follow-up in ado-aw.
The companion version-bump PR is titled chore(deps): update AWF_VERSION to 0.25.65.
Releases analyzed
Notable features for ado-aw to adopt
-
Model fallback support documented (v0.25.53): AWF added documentation for a model fallback feature. ado-aw maintainers should review whether the AWF config generated by ado-aw should expose or configure this fallback behavior (e.g., via the engine: front-matter field).
-
Pre-startup model validation via requestedModel config (v0.25.58): AWF's API proxy now supports a requestedModel config field that enables model validation before the agent container starts. ado-aw generates the AWF config; consider populating this field from the engine.model front-matter value so misconfigured model names are caught at startup rather than at first API call.
This issue was opened automatically by the dependency version updater workflow.
Generated by Dependency Version Updater · sonnet46 4.2M · ◷
Release Notes Action Items for
awf0.25.48→0.25.65This issue summarizes upstream release notes for the
awfdependency between the previously pinned version (0.25.48) and the new pinned version (0.25.65), highlighting items that may need follow-up in ado-aw.The companion version-bump PR is titled
chore(deps): update AWF_VERSION to 0.25.65.Releases analyzed
Notable features for ado-aw to adopt
Model fallback support documented (v0.25.53): AWF added documentation for a model fallback feature. ado-aw maintainers should review whether the AWF config generated by ado-aw should expose or configure this fallback behavior (e.g., via the
engine:front-matter field).Pre-startup model validation via
requestedModelconfig (v0.25.58): AWF's API proxy now supports arequestedModelconfig field that enables model validation before the agent container starts. ado-aw generates the AWF config; consider populating this field from theengine.modelfront-matter value so misconfigured model names are caught at startup rather than at first API call.This issue was opened automatically by the dependency version updater workflow.