Release Notes Action Items for awf 0.25.65 → 0.27.0
This issue summarizes upstream release notes for the awf dependency between the previously pinned version (0.25.65) and the new pinned version (0.27.0), 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.0.
Releases analyzed
Notable features for ado-aw to adopt
-
Azure/AWS/GCP OIDC support in Copilot API proxy (v0.25.66): fix(api-proxy): add Azure/AWS/GCP OIDC support to Copilot adapter — AWF's API proxy can now authenticate to Copilot using cloud-native OIDC tokens (Azure workload identity, AWS IAM, GCP service accounts). ado-aw could surface this as a new auth option for pipelines running in Azure-hosted environments, potentially removing the need to manage long-lived tokens.
-
cli-proxy: fail fast on DIFC proxy unreachability (v0.25.66): [awf] cli-proxy: fail fast on external DIFC proxy unreachability — The CLI proxy now immediately errors out (rather than hanging) if the external DIFC proxy is unreachable. This is a behavioral change: pipelines that previously stalled on DIFC proxy issues will now fail faster with a clearer error. ado-aw maintainers should verify that DIFC proxy configuration is correct before this upgrade lands.
-
Integration ID forwarding fix (v0.25.67): fix: forward GITHUB_COPILOT_INTEGRATION_ID to api-proxy as COPILOT_INTEGRATION_ID — ado-aw sets GITHUB_COPILOT_INTEGRATION_ID for telemetry/billing identification. This fix ensures it is correctly forwarded to the AWF api-proxy as COPILOT_INTEGRATION_ID. Verify that the integration ID is appearing correctly in Copilot usage reports after upgrading.
-
PAT-safe integration ID behavior and model name normalization (v0.25.68): fix(api-proxy): restore PAT-safe integration ID behavior and normalize dated CAPI model names — Restores PAT token-safe behavior for the integration ID (a regression fix from v0.25.67) and normalizes older Copilot API model name formats. If ado-aw pins specific model names that use legacy CAPI naming, they may be transparently normalized after this upgrade.
This issue was opened automatically by the dependency version updater workflow.
Generated by Dependency Version Updater · sonnet46 3M · ◷
Release Notes Action Items for
awf0.25.65→0.27.0This issue summarizes upstream release notes for the
awfdependency between the previously pinned version (0.25.65) and the new pinned version (0.27.0), 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.0.Releases analyzed
Notable features for ado-aw to adopt
Azure/AWS/GCP OIDC support in Copilot API proxy (v0.25.66):
fix(api-proxy): add Azure/AWS/GCP OIDC support to Copilot adapter— AWF's API proxy can now authenticate to Copilot using cloud-native OIDC tokens (Azure workload identity, AWS IAM, GCP service accounts). ado-aw could surface this as a new auth option for pipelines running in Azure-hosted environments, potentially removing the need to manage long-lived tokens.cli-proxy: fail fast on DIFC proxy unreachability (v0.25.66):
[awf] cli-proxy: fail fast on external DIFC proxy unreachability— The CLI proxy now immediately errors out (rather than hanging) if the external DIFC proxy is unreachable. This is a behavioral change: pipelines that previously stalled on DIFC proxy issues will now fail faster with a clearer error. ado-aw maintainers should verify that DIFC proxy configuration is correct before this upgrade lands.Integration ID forwarding fix (v0.25.67):
fix: forward GITHUB_COPILOT_INTEGRATION_ID to api-proxy as COPILOT_INTEGRATION_ID— ado-aw setsGITHUB_COPILOT_INTEGRATION_IDfor telemetry/billing identification. This fix ensures it is correctly forwarded to the AWF api-proxy asCOPILOT_INTEGRATION_ID. Verify that the integration ID is appearing correctly in Copilot usage reports after upgrading.PAT-safe integration ID behavior and model name normalization (v0.25.68):
fix(api-proxy): restore PAT-safe integration ID behavior and normalize dated CAPI model names— Restores PAT token-safe behavior for the integration ID (a regression fix from v0.25.67) and normalizes older Copilot API model name formats. If ado-aw pins specific model names that use legacy CAPI naming, they may be transparently normalized after this upgrade.This issue was opened automatically by the dependency version updater workflow.