Conversation
Merged
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
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.
Routine dependency bumps. Every pin stays exact (
==/ bare version); nothing was widened.Backend
openaipypdfpypdfium2uvicorn[standard]ruffmkdocs-materialandmkdocs-include-markdown-plugin(docs group) are already current.Frontend
@lucide/vuepiniavitevitestvue-tscglobalsAlso
npm audit fix, which lifts the transitivenanoid3.3.17 → 3.3.18 in the lockfile (GHSA-2v37-7h3g-55p8, high).npm auditnow reports 0 vulnerabilities. No direct pin changed as a result.THIRD_PARTY_NOTICES.mdregenerated — versions only, no license changes.Two deliberately held back
openai2.54.0, not 3.3.1. 3.0.0 makes HTTPX2 the default HTTP client and stops installinghttpx. Both SDK call sites (utils/llm_detection.py,services/vision_llm_ocr.py) pass a customhttpx.AsyncClient(follow_redirects=False, timeout=…)— that client is how the repo's "no redirect following, explicit timeouts" SSRF rule is enforced on the LLM and OCR paths. Migrating means addinghttpx2, rewriting both call sites, and living with both httpx generations in the image (the docling and probe clients stay on httpx v1). That is a migration with security-relevant surface, not a version bump, so it belongs in its own PR.typescript6.0.3, not 7.0.2.package.jsonalready documents why: typescript-eslint 8.x requirestypescript <6.1.0, and vue-tsc has no TS 7 support. Left alone.Verification
uv run ruff check+format --check, 381 pytest,npm run check,npm run build, 12 Playwright e2e — all pass.