deps(deps): Bump pymupdf from 1.27.2.2 to 1.28.0#3
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
exbuf
added a commit
that referenced
this pull request
Jul 2, 2026
inaccurate --on-match claim on --watch composition Two things in one commit — the second was uncovered while writing the first, so they need to land together for the README to stay factually correct. 1. **--on-match accuracy fix (README).** The "How these compose" section added in e8d10fd claimed --watch could pair with --on-match ("--on-match CMD for a live pattern sentinel"). Verified against the code: --watch returns from run_watch() at cli.py:1586, BEFORE the on-match hook code around line 871. peekdocs/watcher.py has zero on_match references. --on-match is a batch-search hook (one hook per invocation); --watch's notification channel is the stdout NDJSON stream. Rewrites composition #1 to reflect that, with an explicit note calling out the difference so future readers don't fall into the same trap. 2. **Worked examples cross-linked from all three README compositions.** Compositions #2 (provenance audit) and #3 (scheduled pattern scan) already had worked examples in USER_GUIDE.md (audit engagement provenance, line 1496; nightly source-tree watch, line 1419). Added cross-links in the README so readers don't have to hunt for them. 3. **New worked example: real-time pattern monitoring with --watch.** Composition #1 had no worked example — the "nightly source-tree watch" one uses cron, not the --watch flag. Added a full walkthrough in USER_GUIDE.md right after the audit engagement one: - Domain-neutral scenario (docs team hygiene watch — TODO markers, deprecated feature names, internal-only URLs). Deliberately not a compliance / credential scanning framing. - Setup: build regex collection in GUI. - Command: --watch --regex-collection piped to a shell loop that fires osascript display notifications. - Accurate NDJSON output shape (7 fields, verified against peekdocs/watcher.py's docstring). - Variations: Slack webhook, log-to-disk, jq prefilter. - Six gotchas: --on-match doesn't fire in --watch, Ctrl-C clean shutdown, refuse-to-run-as-root, --allow-system-paths warning, no delete events, noisy folders. - What this is not: pre-commit hook substitute. 4. USER_GUIDE TOC entry added for the new worked example. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
exbuf
added a commit
that referenced
this pull request
Jul 2, 2026
adopters see themselves first; drop artificial "Home user" identity segregation The list opened with **Home user** (least likely PyPI/GitHub discoverer) and buried the technical roles most likely to reach peekdocs through Python-packaging channels at positions #10–12 (AI/ML engineer, Engineer, Developer / programmer). A first-time visitor arriving from a GitHub search for "python document search cli" scrolled past four non-technical bullets before seeing themselves. Also, having **Home user** as one bullet among "Office worker / Developer / Sysadmin" implicitly framed the other 12 bullets as NOT home users — contradicting the "entirely on your own computer" opening. peekdocs is local-only; every user IS a home user. **Reordered** so tech-heavy adopters land at the top: 1. Developer / programmer (was #12) 2. Sysadmin (was #6) 3. AI/ML engineer (was #10) 4. IT consultant (was #4, expanded) 5. Data researcher (was #9) 6. Engineer (was #11) 7. Documentation team (was #7) 8. Auditor or review (was #5) 9. Researcher (was #8) 10. Small business owner (was #3, absorbed the Home-user tax-search scenario as a "Personal side" note) 11. Office worker (was #2) **Dropped two bullets:** - **Home user** — the "everybody is a home user" framing now lives in the section's opening paragraph ("entirely on your own computer"), applying to every bullet rather than being one bullet's identity. The tax-search scenario is folded into Small business owner as a "Personal side" note so no concrete example is lost. - **Email archives** — was a file type, not a role. Odd one out in a role-shaped list. Already covered by the intro's file-type enumeration (Word, PDF, Excel, email, scanned documents, archives, and 100+ more). **Enhanced two one-liners:** - **Sysadmin** was "Search 20 GB of log files for a request ID across mixed archives." Added the `.gz`/`.bz2`/`.zip`/`.tar` detail (read natively without unpacking) and the --watch NDJSON streaming detail for pipeline integration. - **IT consultant** was "Search a folder of client documents for a set of terms." Added the standalone-binary-on-USB workflow (--output-dir back to the USB, --no-index for zero artifacts) and a cross-link to the Portable / consulting use section added earlier this session (fc9fd98). All other bullets keep their descriptions verbatim — only their position in the list changed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
exbuf
added a commit
that referenced
this pull request
Jul 2, 2026
README + USER_GUIDE audit (PDF line-vs-paragraph framing, composition-row labeling) Two small fixes surfaced by a comprehensive accuracy + consistency audit. README came back completely clean; USER_GUIDE had two items worth fixing: **1. Line 735 — PDF framing inconsistent with the canonical line/paragraph/row rule.** The -P (line-proximity) row in Flag Use Summary said "for PDF, a line is a text block (variable)" while every other place in the doc — CLI --help, tooltip (fixed earlier this session in c7d148f), the CLI's line 768 neighbor, and the four other spots documented in project memory (project_lines_vs_paragraphs_concept.md) — uses "paragraph" for PDF. Merged Word and PDF into one clause: "for plain text and source code, a line is a literal line; for Word (.docx) and PDF, a line is a paragraph; for Excel, a line is a row" Now consistent with the tooltip fix and the canonical framing. **2. Composition rows 196–197 relabeled to make variant relationship unambiguous.** The Complete CLI Reference has a Compositions cluster (rows 193–197). Three composition names (rows 193–195: Live pattern sweep, Provenance audit, Scheduled pattern scan) plus two extra rows (196, 197) that were variants of composition #3 but labeled generically: Before: 196 | Scheduled scan with match-only notification 197 | Scheduled scan with hash provenance for later diffing After: 196 | Scheduled pattern scan — variant with match-only notification (extends row 195) 197 | Scheduled pattern scan — variant with hash provenance for later diffing (extends row 195) The three-vs-five ambiguity is now resolved at the row level. A reader scanning the cluster sees three named compositions plus two clearly-labeled variants of #3 — matches the intro paragraph's claim of "three named compositions from the README's How these compose section." Non-issues explicitly checked and skipped: - Historical version breadcrumbs (1.2.6, 1.2.8) at lines 366, 384, 386 — user decided in the previous audit these are style breadcrumbs, not stale. - Line 3505 "reports remain English" — auditor initially flagged as potentially misleading next to the "seven languages" claim, but the English-only list right below makes clear which surfaces do and don't translate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bumps [pymupdf](https://github.com/pymupdf/pymupdf) from 1.27.2.2 to 1.28.0. - [Release notes](https://github.com/pymupdf/pymupdf/releases) - [Changelog](https://github.com/pymupdf/PyMuPDF/blob/main/changes.txt) - [Commits](pymupdf/PyMuPDF@1.27.2.2...1.28.0) --- updated-dependencies: - dependency-name: pymupdf dependency-version: 1.27.2.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/pip/pymupdf-1.27.2.3
branch
from
2cf1126 to
103a160
Compare
exbuf
added a commit
that referenced
this pull request
Jul 6, 2026
The Installation nav list and its five section headings now carry matching numbers: 1. Option A: Standalone Download (no Python needed) 2. Option B: Quick Install with pipx (for Python users) 3. Prerequisites 4. Upgrading 5. Uninstalling Numbering the headings changes their GitHub anchor fragments (#prerequisites → #3-prerequisites etc.), so every reference was rewritten in the same commit: README.md 15 refs (5 nav links + 10 in-document cross-references: Option B pointers in Option A's prose, Uninstalling from the standalone-upgrade note, Upgrading from factory reset, Prerequisites from the file-types tables and platform notes, Option A from the corporate-firewall note and install chooser) docs/USER_GUIDE.md 3 refs (../README.md#prerequisites → #3-prerequisites: OCR flag row, -O requirement note, dependencies section) docs/TROUBLESHOOTING.md 2 refs (Tesseract install pointer + the pipx-instead-of-venv suggestion) Pre-flight checked that no doc links to another file's own #prerequisites-style anchor (e.g., docs/INSTALLATION.md has no inbound #prerequisites deep links), so the global rewrite is collision-free. Verified zero stale old-anchor references remain across the three touched files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
exbuf
added a commit
that referenced
this pull request
Jul 7, 2026
The TOC sat between 'How these compose' and 'CLI at a Glance', roughly halfway down the file — after a reader had already scrolled past Installation, Quick Start, the persona list, five demo clips, and the feature sections. A TOC you reach after consuming half the document navigates nothing. Moved to line 133, immediately after the hero GIF and before ## Installation. New reading order for a first-time visitor: title → language fold → lead → hero clip → Contents → Install. Also rebuilt the TOC itself, which had two defects: 1. Stale order — it still listed 'Who Is It For?' first and Installation 8th, reflecting the pre-restructure document. Entries now match the actual section order top to bottom (Installation → Quick Start → Who Is It For → ... → License). 2. A corrupted entry — the earlier Installation-anchor rewrite (f4bf209) globally replaced '#prerequisites' with '#3-prerequisites' and the nav-numbering sed also caught the TOC's own '- [Prerequisites]' bullet, mangling it into '3. [Prerequisites](#3-prerequisites)' mid-list. The rebuild drops the Prerequisites entry from the TOC entirely — the Installation entry covers it; subsection-level links live in Installation's own nav list. Line count 1004 → 1001 (TOC shrank by dropping the Prerequisites sub-entry and normalizing blanks). No inbound '#contents' links exist anywhere in the repo, so the section move breaks nothing. Co-Authored-By: Claude Opus 4.7 (1M context) <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
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 pymupdf from 1.27.2.2 to 1.28.0.
Release notes
Sourced from pymupdf's releases.
Changelog
Sourced from pymupdf's changelog.
... (truncated)
Commits
e9cdfc9changes.txt: fix mupdf version number.629a358docs/document.rst: add new in 1.28.0 to init's archive.7264f27README.md: updated example conversion from md to pdf.119a0bcdocs/document.rst: document that save() now also works for non-pdf documents.5ebfc4csetup.py: use mupdf-1.28.0.14d8facchanges.txt: removed bogus #4423 entry, added #5033.d961616tests/test_annots.py: added test_5033() for setRect() vs set_rect() bug.d91bd63changes.txt: added note about save() and non-pdf documents.fd409de.github/workflows/: updated to use mupdf branch 1.28.x.04aa7ddRemove old setRect Name