Update dev pillow pin to 12.3 - #6836
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Merging this PR will not alter performance
Comparing Footnotes
|
Greptile SummaryUpdates the development lockfile from Pillow 12.2.0 to 12.3.0 to address reported vulnerabilities.
Confidence Score: 5/5The PR appears safe to merge with no actionable changed-code failures identified. The lockfile change is confined to Pillow 12.3.0 artifacts, while the unrelated vulnerable aiohttp version reported in dependency context is identical on the base and head revisions.
|
| Filename | Overview |
|---|---|
| uv.lock | Updates the locked Pillow package and its distribution artifacts from 12.2.0 to 12.3.0; no actionable changed-code defect was established. |
| news/6836.chore.md | Adds a concise changelog entry describing the development dependency security update. |
Reviews (1): Last reviewed commit: "add news fragment" | Re-trigger Greptile
* Update dev pillow pin to 12.3 (#6836) * Bump locked aiohttp and cryptography for HIGH severity CVEs Dependabot flagged two transitive dependencies in uv.lock: aiohttp 3.14.1 -> 3.14.3 (GHSA-cq5v-8q36-5273 / CVE-2026-69244) cryptography 49.0.0 -> 50.0.0 (GHSA-g6cj-pr64-35w5 / CVE-2026-69247) Both reach the lock only through the docs app: reflex-enterprise pulls asgiproxy (-> aiohttp) and joserfc (-> cryptography). Neither is a dependency of the published reflex package, so this is a lockfile-only fix with no impact on installs of reflex itself. aiohttp 3.14.3 published outside the 7 day exclude-newer window and resolves on its own. cryptography 50.0.0 published inside it, so add an exclude-newer exemption alongside the existing starlette one. Since cryptography is transitive there is no version floor to pin, and the exemption keeps future security releases resolvable immediately rather than aging out of the window first. Verified the patched versions against their consumers: joserfc 1.7.1 round-trips a JWT on cryptography 50.0.0, and asgiproxy 0.2.0 imports cleanly on aiohttp 3.14.3. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ULSRWe743saVEBbvBxuL9D * Rename chore news fragments to misc so they materialize `chore` is not a configured towncrier type in pyproject.toml (the types are breaking, deprecation, feature, bugfix, performance, docs, misc), so `_has_pending_fragments()` in scripts/release.py skipped these files and they would never have reached a CHANGELOG: news/6836.chore.md -> news/6836.misc.md news/+sec-aiohttp-cryptography.chore.md -> news/+sec-aiohttp-cryptography.misc.md Both now render under the Miscellaneous heading, verified with `towncrier build --draft`. Also expand the dependency-bump entry: the aiohttp 3.14.1 -> 3.14.3 jump clears CVE-2026-59881 and CVE-2026-69243 (both fixed in 3.14.2) in addition to the reported CVE-2026-69244, and the entry now notes these are docs-app transitive dependencies rather than shipped ones. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ULSRWe743saVEBbvBxuL9D * Name the dependency-bump news fragment after PR #6837 Replaces the `+`-prefixed placeholder now that the PR number is known, so the changelog entry links back to the pull request. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ULSRWe743saVEBbvBxuL9D --------- Co-authored-by: Claude <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.