Floor je_auto_control at the release that fixes the pillow CVEs#469
Merged
Conversation
requirements.txt asked for je_auto_control unpinned, so the dependency graph resolved it to whatever was published — 0.0.214, which pins pillow==12.2.0 and pulls 13 open CVEs in transitively. 0.0.216 ships pillow==12.3.0. The floor is also what makes the alerts close: GitHub re-resolves a pip manifest when the file changes, not when a transitive dependency's upstream gets a new release, so the alerts sat untouched since 2026-07-21 while pyproject.toml and uv.lock moved on without them.
|
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
1 participant
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.
The 13 pillow alerts did not close after publishing 0.0.216, and they were not going to.
requirements.txtlistedje_auto_controlwith no constraint, so GitHub's dependency graph resolved it to the published release and recorded its transitivepillow==12.2.0. GitHub re-resolves a pip manifest when the file changes, not when a transitive dependency's upstream ships a fix — every alert still readsupdated_at: 2026-07-21whilepyproject.tomlanduv.lockmoved to 12.3.0 today. The SBOM shows both entries side by side:pillow 12.2.0(from requirements.txt) andpillow 12.3.0(from the pinned manifests).A floor rather than a pin: it states the real requirement (0.0.216 is the first release carrying
pillow==12.3.0), forces the re-resolution that closes the alerts, and does not need editing on every release — which matters now that merging to main cuts one.