deps(deps): Bump pillow from 12.1.1 to 12.2.0#2
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.1.1 to 12.2.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.1.1...12.2.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 12.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
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>
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 pillow from 12.1.1 to 12.2.0.
Release notes
Sourced from pillow's releases.
... (truncated)
Commits
3c41c0912.2.0 version bumpcdaa29eCheck calloc return value (#9527)585b2f5Check calloc return valueecf011eCheck all allocs in the Arrow tree (#9488)cf6de8cReject non-numeric elements inside list coords (#9526)ffdcedeUpdate 12.2.0 release notes (#9522)7929d77Added security release notes (#149)c4f7aa5Added security release notes22cdb5fMove variable declaration inside define (#9525)fc15b3bResize tall images vertically first (#9524)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)