Skip to content

Bump firewall version to v0.25.43 #31376

@lpcox

Description

@lpcox

Summary

Bump the default Agent Workflow Firewall (AWF) version from v0.25.42 to v0.25.43.

Changes Required

File: pkg/constants/version_constants.go

// Before
const DefaultFirewallVersion Version = "v0.25.42"

// After
const DefaultFirewallVersion Version = "v0.25.43"

Changelog (since v0.25.41)

New features

ARC/DinD support

Bug fixes & refactoring

New Frontmatter / Config Fields for gh-aw Compiler

The following new AWF config properties should be considered for exposure through gh-aw workflow frontmatter:

1. container.dockerHostPathPrefix (string)

container:
  dockerHostPathPrefix: /host

CLI: --docker-host-path-prefix /host

Prefixes all AWF bind-mount source paths so a Docker daemon with a separate filesystem can resolve them. Essential for ARC DinD sidecar runners. Kernel virtual filesystems (/dev, /sys, /proc) are automatically excluded.

Frontmatter suggestion: firewall.container.dockerHostPathPrefix or a simpler firewall.arc-dind-prefix.

2. apiProxy.maxRuns (integer)

apiProxy:
  maxRuns: 100

CLI: --max-runs 100

Hard cap on the number of LLM API invocations per workflow run. Complements the existing maxEffectiveTokens budget guard. Returns HTTP 429 with max_runs_exceeded error type when exceeded.

Frontmatter suggestion: firewall.apiProxy.maxRuns — useful for cost-control guardrails in agentic workflows.

3. apiProxy.auth (object)

apiProxy:
  auth:
    type: github-oidc
    provider: azure
    azureTenantId: "..."
    azureClientId: "..."

Enables OIDC-based credential exchange — agents can reach Azure OpenAI, AWS Bedrock, or GCP Vertex AI without static API keys by exchanging GitHub OIDC tokens for cloud provider tokens.

Frontmatter suggestion: firewall.apiProxy.auth.* — enables keyless LLM access in enterprise environments. Requires id-token: write permission.

Checklist

  • Update DefaultFirewallVersion in pkg/constants/version_constants.go
  • Run make build to rebuild the binary
  • Run make recompile to regenerate all lock files with the new version
  • Run make agent-finish to validate
  • Verify lock files reference the new firewall version
  • Evaluate new config fields (dockerHostPathPrefix, maxRuns, auth) for frontmatter exposure

References

Metadata

Metadata

Assignees

Labels

dependenciesPull requests that update a dependency file

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions