Repository navigation
fix(security): release RC.2 with pypdf 6.21.4 - #24
Merged
Merged
Conversation
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.
RC.1 pins pypdf 6.21.2, now affected by seven high-severity advisories. RC.2 requires and hash-locks 6.21.4, with regression assertions excluding affected versions. Other dependency versions and the operator contract stay unchanged.
Validation passed: target tests twice (40 each); Python 3.12/3.13 full suites: 3563 passed / 3 skips each; ARM64 suite: 3536 passed / 21 environment skips; 277/277 adversarial cases; 44/44 actual-model E2E; fresh OSV all four locks and installed environments: 0 findings. Signed clean installation and RC.1→RC.2 upgrade/rollback passed on macOS and ARM64 Linux. Exact-commit native CI: https://github.com/talos-kernel/Talos/actions/runs/41291524692.
An initial supplemental Pi source-check harness omitted status.json while adding install.sh. The matching committed test input was added; version tests passed twice and the full suite passed. Signed archive bytes were unchanged. Stable remains gated on seven new deployed observation days.