Bump gh-aw to v0.75.0#165
Merged
Merged
Conversation
Updates gh-aw from v0.74.8 to v0.75.0 across all version pins and recompiles all 10 lock files. Picks up gh-aw-mcpg v0.3.17 and gh-aw-firewall v0.25.51, which may resolve the MCP JSONL permission denied error observed with v0.3.9. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
actions-lock.json,pre-commit.yml,check-aw-updates.yml,run-gh-aw-compile.sh)gh-aw-mcpg:v0.3.17(was v0.3.9) andgh-aw-firewall:v0.25.51(was v0.25.49)Motivation
v0.74.8 produced an MCP agent failure on
elastic/docs-contentPRs with two symptoms:open /tmp/gh-aw/mcp-logs/rpc-messages.jsonl: permission denied— container ownership issue in mcpg v0.3.9, potentially fixed in the v0.3.9→v0.3.17 jumpResult too large: 17969 > 16384— WASM guard 16KB cap hit by the docs-content PR API response; not addressed in release notes through v0.75.0, needs upstream bug reportTest plan
🤖 Generated with Claude Code