Skip to content

PDFCAB 1.18.0

Choose a tag to compare

@SybilGambleyyu SybilGambleyyu released this 07 Aug 06:58

Current coverage requirement control

  • Adds a deterministic pair where both PDFs retain the same well-formed semantic ByteRange before their current physical ends.
  • The candidate adds a distinct incremental revision, while coverage counts remain unchanged.
  • Requires PFP010 and no coverage-change event, distinguishing a current-boundary requirement from PFP009's regression-only behavior.

The fixture asserts only static public outputs; it makes no signature-validity, certificate, permission, or trust claim and publishes no offset, signature content, or hash.

Verification

85 tests and Ruff passed; the PDFFence 1.18 source candidate scored 155/155 through the process-bound public CLI. Two fixed-timestamp builds produced identical wheel and source archives, and clean wheel/source installs passed pip check, fixture verification, and the complete score.