Repository navigation
build: synchronize dependency pins and service locks - #22
Merged
Merged
Conversation
Signed-off-by: lEWFkRAD <SJWATTS89@OUTLOOK.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
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.
Replace overlapping dependency PRs #13 and #19 with one consistent update: AnyDoc 0.2.4, MCP 2.1.1 and OpenAI 3.19.2, synchronized across plugin/service requirements and both Windows hash locks. Regenerate locks with the repository-required uv 0.12.3. Update the reviewed AnyDoc assertion and make the existing retention fixture deterministically old on Windows, preserving unsafe/arbitrary-directory protections.
Validation: clean dependency environment; AnyDoc import; 175 Python tests plus 14 subtests; 26 Node release tests; both lock validators; compileall; runtime, development and installed-environment audits all passed. Final retention fixture change passed its focused tests. Hosted Windows/Linux and release-archive checks must pass before merge. No live OCR, document processing, deployment or service changes.
AI assistance: Codex prepared and reviewed the repair.