chore(deps): bump requests from 2.32.3 to 2.32.4 in /pmoves/services/pdf-ingest in the pip group across 1 directory - #714
Merged
POWERFULMOVES merged 1 commit intoFeb 26, 2026
Conversation
Bumps the pip group with 1 update in the /pmoves/services/pdf-ingest directory: [requests](https://github.com/psf/requests). Updates `requests` from 2.32.3 to 2.32.4 - [Release notes](https://github.com/psf/requests/releases) - [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md) - [Commits](psf/requests@v2.32.3...v2.32.4) --- updated-dependencies: - dependency-name: requests dependency-version: 2.32.4 dependency-type: direct:production dependency-group: pip ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
deleted the
dependabot/pip/pmoves/services/pdf-ingest/pip-512858e340
branch
February 26, 2026 16:47
POWERFULMOVES
added a commit
that referenced
this pull request
Feb 27, 2026
* feat: harden topology+CHIT production gate workflow (#712) * feat(preflight): add topology and CHIT sync gate * feat(preflight): expand topology gate to all running containers * feat(preflight): enforce manifest-driven topology policy gate * feat(preflight): scope CHIT gate to policy-defined services * feat(runtime): enforce CHIT production overlays on core services * docs(ops): add topology+CHIT strict gate workflow runbook * chore(chit): sync secrets manifest v1 with v2 source * fix(make): run CHIT manifest targets with project venv * fix(topology-gate): make archon-ui absence non-fatal, align policy networks - archon-ui missing is now a warning (headless deployments via `make up-agents` exclude it intentionally) - archon-ui policy network changed from pmoves_external to pmoves_api to match compose wiring Resolves review comments on PR #712. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Shaela Bello <slbello@uncg.edu> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> * chore: sync 14 submodules to latest PMOVES.AI-Edition-Hardened Updated gitlinks for: A2UI, AgentGym, Archon, BoTZ, Creator, Danger-infra, DoX, Headscale, MAI-UI, n8n, surf, tensorzero, cipher, e2b-mcp-server. Resolves branch/detached-HEAD misalignment after PR #714/#715 merge into main. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: point PMOVES-surf gitlink to PMOVES.AI-Edition-Hardened branch PMOVES-surf was the only submodule (1/40) still pointing to main (135748a) instead of the hardened branch (a27fbb2). The hardened branch includes 3 additional integration dossier commits. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * docs: add PMOVES.AI integration dossiers to 5 submodules Create PMOVES.AI_INTEGRATION.md for submodules that were missing the required integration dossier, fixing submodule-layer-validate and submodule-docs-audit audit gate failures: - PMOVES-AgentGym (worker: RL training environments) - Pmoves-cipher (agent: dual-layer memory, port 8096) - pmoves-e2b-mcp-server (worker: sandboxed code execution) - PMOVES-Headscale (agent: VPN control plane) - PMOVES-n8n (orchestration: 11 workflow definitions) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: update audit evidence and secrets manifest after post-sync validation Regenerated evidence files from submodule-layer-validate-all-strict (40/40 pass), secrets-funnel sync (99 entries), and tooling audit. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: flatten CHIT_PASSPHRASE compose substitution and document passphrase setup The topology-chit-gate-strict audit gate warned about empty/placeholder CHIT_PASSPHRASE on hi-rag-gateway, hi-rag-gateway-v2, and agent-zero. Root cause: Docker Compose environment: section interpolation uses shell env / --env-file / .env — NOT env_file: loaded values. The nested ${CHIT_PROD_PASSPHRASE:-${JWT_SECRET:-}} never resolved because neither variable was available at compose parse time. Changes: - Flatten all 7 CHIT_PASSPHRASE lines in docker-compose.yml to ${CHIT_PROD_PASSPHRASE:-changeme} (changeme is in the gate's PLACEHOLDER_VALUES set, catching forgotten deployments) - Update env.shared.example with generation command - Document passphrase setup in TOPOLOGY_CHIT_GATE_WORKFLOW.md and ENVIRONMENT_SETUP.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: resolve hi-rag v1 port conflict, add evo-controller Dockerfile, fix build contexts Three compose fixes surfaced during topology gate validation: 1. hi-rag-gateway v1 shared HIRAG_V2_HOST_PORT with v2, causing port collision when set to 8086. Give v1 its own HIRAG_V1_HOST_PORT variable (default 8089). 2. evo-controller had no Dockerfile — create one following the flute-gateway pattern (python:3.11-slim, non-root user, healthcheck). Includes services/common/ for shared env module import. 3. Both evo-controller and flute-gateway used wrong build context (./services/<name> instead of .). Fix to match hi-rag-gateway pattern: context=. with dockerfile=services/<name>/Dockerfile. Also adds both in-tree services to images.yaml for CI builds. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: add FFmpeg/WebRTC build deps to flute-gateway Dockerfile PyAV (av) and aiortc require system build dependencies (gcc, python3-dev, FFmpeg dev headers, libopus, libvpx) to compile from source. Added them to the install layer and a cleanup step that purges build-only deps after pip install to keep the final image slim. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address PR #716 review comments — multi-stage build, fail-fast secrets, portable paths - Convert flute-gateway Dockerfile to multi-stage build: builder stage compiles PyAV/aiortc wheels, runtime stage installs only shared libs (libavformat61, libavcodec61, etc.) — eliminates --auto-remove risk of purging runtime .so files (Critical fix from CodeRabbit) - Replace CHIT_PASSPHRASE fallback ${:-changeme} with ${:?message} across all 7 compose occurrences so services fail-fast when CHIT_PROD_PASSPHRASE is not set in env.shared - Fix hardcoded Windows paths in 41 evidence JSON files and their generation scripts (submodule_layer_validate.py, runall.py) to use project-relative paths instead of absolute C:\Users\... paths - Add cross-platform (PowerShell) passphrase generation instructions to ENVIRONMENT_SETUP.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: set CHIT_PROD_PASSPHRASE in CI compose validation step The ${:?} fail-fast guard requires CHIT_PROD_PASSPHRASE to be set. CI copies env.shared.example (which has an empty value) so compose config would fail. Add env var and --env-file to the validation step. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * docs: make env.shared passphrase setup idempotent Replace append-only `printf >>` / `Add-Content` with grep+sed (bash) and Get-Content + -replace (PowerShell) patterns so re-running the snippet updates existing entries instead of duplicating them. Addresses PR #716 CodeRabbit nitpick comment #6. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: add gh auth token fallback to GHCR bootstrap in push-gh-secrets The GHCR bootstrap token resolution now falls back to `gh auth token` when neither GHCR_TOKEN nor GH_PAT_PUBLISH are set, matching the existing username fallback pattern that already uses `gh api user`. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Shaela Bello <slbello@uncg.edu> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
POWERFULMOVES
added a commit
that referenced
this pull request
Feb 28, 2026
* feat: harden topology+CHIT production gate workflow (#712) * feat(preflight): add topology and CHIT sync gate * feat(preflight): expand topology gate to all running containers * feat(preflight): enforce manifest-driven topology policy gate * feat(preflight): scope CHIT gate to policy-defined services * feat(runtime): enforce CHIT production overlays on core services * docs(ops): add topology+CHIT strict gate workflow runbook * chore(chit): sync secrets manifest v1 with v2 source * fix(make): run CHIT manifest targets with project venv * fix(topology-gate): make archon-ui absence non-fatal, align policy networks - archon-ui missing is now a warning (headless deployments via `make up-agents` exclude it intentionally) - archon-ui policy network changed from pmoves_external to pmoves_api to match compose wiring Resolves review comments on PR #712. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Shaela Bello <slbello@uncg.edu> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> * chore: sync 14 submodules to latest PMOVES.AI-Edition-Hardened Updated gitlinks for: A2UI, AgentGym, Archon, BoTZ, Creator, Danger-infra, DoX, Headscale, MAI-UI, n8n, surf, tensorzero, cipher, e2b-mcp-server. Resolves branch/detached-HEAD misalignment after PR #714/#715 merge into main. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: point PMOVES-surf gitlink to PMOVES.AI-Edition-Hardened branch PMOVES-surf was the only submodule (1/40) still pointing to main (135748a) instead of the hardened branch (a27fbb2). The hardened branch includes 3 additional integration dossier commits. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * docs: add PMOVES.AI integration dossiers to 5 submodules Create PMOVES.AI_INTEGRATION.md for submodules that were missing the required integration dossier, fixing submodule-layer-validate and submodule-docs-audit audit gate failures: - PMOVES-AgentGym (worker: RL training environments) - Pmoves-cipher (agent: dual-layer memory, port 8096) - pmoves-e2b-mcp-server (worker: sandboxed code execution) - PMOVES-Headscale (agent: VPN control plane) - PMOVES-n8n (orchestration: 11 workflow definitions) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: update audit evidence and secrets manifest after post-sync validation Regenerated evidence files from submodule-layer-validate-all-strict (40/40 pass), secrets-funnel sync (99 entries), and tooling audit. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: flatten CHIT_PASSPHRASE compose substitution and document passphrase setup The topology-chit-gate-strict audit gate warned about empty/placeholder CHIT_PASSPHRASE on hi-rag-gateway, hi-rag-gateway-v2, and agent-zero. Root cause: Docker Compose environment: section interpolation uses shell env / --env-file / .env — NOT env_file: loaded values. The nested ${CHIT_PROD_PASSPHRASE:-${JWT_SECRET:-}} never resolved because neither variable was available at compose parse time. Changes: - Flatten all 7 CHIT_PASSPHRASE lines in docker-compose.yml to ${CHIT_PROD_PASSPHRASE:-changeme} (changeme is in the gate's PLACEHOLDER_VALUES set, catching forgotten deployments) - Update env.shared.example with generation command - Document passphrase setup in TOPOLOGY_CHIT_GATE_WORKFLOW.md and ENVIRONMENT_SETUP.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: resolve hi-rag v1 port conflict, add evo-controller Dockerfile, fix build contexts Three compose fixes surfaced during topology gate validation: 1. hi-rag-gateway v1 shared HIRAG_V2_HOST_PORT with v2, causing port collision when set to 8086. Give v1 its own HIRAG_V1_HOST_PORT variable (default 8089). 2. evo-controller had no Dockerfile — create one following the flute-gateway pattern (python:3.11-slim, non-root user, healthcheck). Includes services/common/ for shared env module import. 3. Both evo-controller and flute-gateway used wrong build context (./services/<name> instead of .). Fix to match hi-rag-gateway pattern: context=. with dockerfile=services/<name>/Dockerfile. Also adds both in-tree services to images.yaml for CI builds. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: add FFmpeg/WebRTC build deps to flute-gateway Dockerfile PyAV (av) and aiortc require system build dependencies (gcc, python3-dev, FFmpeg dev headers, libopus, libvpx) to compile from source. Added them to the install layer and a cleanup step that purges build-only deps after pip install to keep the final image slim. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address PR #716 review comments — multi-stage build, fail-fast secrets, portable paths - Convert flute-gateway Dockerfile to multi-stage build: builder stage compiles PyAV/aiortc wheels, runtime stage installs only shared libs (libavformat61, libavcodec61, etc.) — eliminates --auto-remove risk of purging runtime .so files (Critical fix from CodeRabbit) - Replace CHIT_PASSPHRASE fallback ${:-changeme} with ${:?message} across all 7 compose occurrences so services fail-fast when CHIT_PROD_PASSPHRASE is not set in env.shared - Fix hardcoded Windows paths in 41 evidence JSON files and their generation scripts (submodule_layer_validate.py, runall.py) to use project-relative paths instead of absolute C:\Users\... paths - Add cross-platform (PowerShell) passphrase generation instructions to ENVIRONMENT_SETUP.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: set CHIT_PROD_PASSPHRASE in CI compose validation step The ${:?} fail-fast guard requires CHIT_PROD_PASSPHRASE to be set. CI copies env.shared.example (which has an empty value) so compose config would fail. Add env var and --env-file to the validation step. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * docs: make env.shared passphrase setup idempotent Replace append-only `printf >>` / `Add-Content` with grep+sed (bash) and Get-Content + -replace (PowerShell) patterns so re-running the snippet updates existing entries instead of duplicating them. Addresses PR #716 CodeRabbit nitpick comment #6. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: add gh auth token fallback to GHCR bootstrap in push-gh-secrets The GHCR bootstrap token resolution now falls back to `gh auth token` when neither GHCR_TOKEN nor GH_PAT_PUBLISH are set, matching the existing username fallback pattern that already uses `gh api user`. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * ci: migrate GHCR auth to GitHub App tokens with PAT+workflow fallback All 4 GHCR-pushing workflows now generate short-lived installation tokens via actions/create-github-app-token using the PMOVES.AI GitHub App (GH_APP_ID + GH_APP_SEC secrets). Each workflow falls back to PAT-based auth then workflow token if the App token is unavailable. integrations-ghcr.yml uses explicit three-tier login steps with a hard-fail guard; the simpler workflows use inline ternary expressions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(ci): remove secrets context from step-level if conditions GitHub Actions does not allow secrets.* in step if: expressions. Remove the guard and rely on continue-on-error: true — if secrets are missing the action fails gracefully, outputs stay empty, and the fallback chain (PAT → workflow token) activates. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(mcp): resolve cipher MCP stdout pollution corrupting stdio transport On Windows, `uv run` activates the venv by sourcing Activate.Ps1 which echoes to stdout, corrupting the MCP JSON-RPC stream. Switch to invoking the venv python directly to bypass activation entirely. Also fix a secondary stdout leak in the NATS announcer (print→stderr), reduce client timeout from 30s→5s, and add health-check + graceful fallback to all cipher slash commands so Docker-offline sessions degrade to local auto-memory instead of hanging. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(mcp): remove unnecessary cwd and PYTHONPATH from cipher MCP config The venv python resolves its own site-packages via .pth files from the editable install — PYTHONPATH is redundant. cwd is also unnecessary since the venv interpreter does not depend on working directory for package resolution. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(mcp): switch cipher MCP from stdio Python bridge to container SSE The local Python subprocess (pmoves-cipher-mcp) caused recurring Activate.ps1 stdout pollution on Windows, corrupting the MCP stdio transport. The cipher-api container already supports SSE natively via @modelcontextprotocol/sdk — enable it and point Claude Code directly at the container's /sse endpoint, eliminating the local bridge entirely. - Enable --mcp-transport-type sse on cipher-api container command - Replace stdio/python MCP config with SSE direct to localhost:8096/sse - No local process, no venv, no Activate.ps1, no stdout corruption Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address PR #719 review comments - Replace sed -i with portable awk+mv for macOS compatibility - Use cryptographic RNG for PowerShell passphrase generation (URL-safe base64) - Update CHIT docs to match actual compose :? (required) syntax - Add _repo_relative_or_posix() helper to handle paths outside repo root - Normalize absolute Windows path in validation evidence JSON - Add traceback.print_exc() for better announcer error diagnostics Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Shaela Bello <slbello@uncg.edu> Co-authored-by: Claude Opus 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.
Bumps the pip group with 1 update in the /pmoves/services/pdf-ingest directory: requests.
Updates
requestsfrom 2.32.3 to 2.32.4Release notes
Sourced from requests's releases.
Changelog
Sourced from requests's changelog.
Commits
021dc72Polish up release tooling for last manual release821770eBump version and add release notes for v2.32.459f8aa2Add netrc file search information to authentication documentation (#6876)5b4b64cAdd more tests to prevent regression of CVE 2024 470817bc4587Add new test to check netrc auth leak (#6962)96ba401Only use hostname to do netrc lookup instead of netloc7341690Merge pull request #6951 from tswast/patch-16716d7cremove linksa7e1c74Update docs/conf.pyc799b81docs: fix dead links to kenreitz.orgDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.