Conversation
* chore: release v0.2.0 First tagged release. Contents of community-improvements project: M1 — Security Hardening (A2A bearer auth, audit redaction, origin verification) M2 — Memory On By Default (session persistence + load-on-start) M3 — Skill Loop (skill-v1 emission + SQLite FTS5 index + curator) Plus: .gitignore cleanup for .automaker-lock + .worktrees, docs coverage of security layer, skill-loop architecture, and new env vars. Manual bump because prepare-release.yml requires GH_PAT secret (not configured). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore: release v0.2.1 Bug fixes from v0.2.0 smoke testing: - Agent card now advertises bearer scheme when A2A_AUTH_TOKEN is set - Session memory persistence actually fires (moved from unreachable on_session_end to after_agent) - Test suite collects cleanly in fresh Docker env - MemoryMiddleware activates standalone (without knowledge_store) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(ci): update repo homepage after docs deploy (#149) Writes the deployed GitHub Pages URL back to the repo's `homepage` field so it renders in the About sidebar on the repo page. Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(llm): override OpenAI SDK User-Agent to bypass Cloudflare WAF Cloudflare's managed WAF on the proto-labs.ai zone returns 403 "Your request was blocked" for any request whose User-Agent starts with `OpenAI/Python` or `AsyncOpenAI/Python` — which is exactly what langchain_openai.ChatOpenAI sends by default via the bundled OpenAI SDK. /v1/models succeeded (different SDK path / UA) while /v1/chat/completions failed, making the break look like a key/ACL issue when it was a header signature match. Reproduction (before fix): curl -H 'User-Agent: OpenAI/Python 1.54.0' -H 'Authorization: Bearer <key>' \ https://api.proto-labs.ai/v1/chat/completions -d '{...}' -> HTTP 403 "Your request was blocked." The same call with User-Agent: curl/*, python-httpx/*, or any non-OpenAI string returns 200. `tools/lg_tools.py:226` already sets a protoAgent UA for outbound HTTP fetches — reuse that identifier here so every egress presents a consistent, allowlisted UA. Alternative fixes considered: - A Cloudflare Custom WAF Skip rule on the hostname: cleaner at the edge but requires a zone-scoped token and couples agent operability to infra config. - Stripping the UA header at cloudflared: not possible; WAF fires before the tunnel sees the request. The in-client override is the most portable fix: self-hosters on a different edge keep working, operators behind Cloudflare stop getting 403s. --------- Co-authored-by: Automaker <automaker@localhost> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Ava <ava@protolabs.ai>
promote: dev → staging (WAF UA fix)
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThe pull request updates the GitHub Actions documentation workflow to automatically update the repository's homepage field to the deployed Pages URL after deployment. It also adds custom HTTP headers to the ChatOpenAI client configuration and bumps the project version to 0.2.1. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
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
Promotes #151/#152 (OpenAI SDK User-Agent override for Cloudflare WAF) from `staging` to `main` for release.
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes