Skip to content

fix(deps): bump epaper-dithering to 6.1.1 for pyo3 security fix - #178

Merged
g4bri3lDev merged 1 commit into
mainfrom
fix/epaper-dithering-6.1.1
Oct 7, 2026
Merged

g4bri3lDev merged 1 commit into
mainfrom
fix/epaper-dithering-6.1.1

Conversation

@g4bri3lDev

Copy link
Copy Markdown
Member

Why

py-opendisplay pins epaper-dithering exactly (==6.1.0), so users, including Home Assistant, only ever get the version pinned here.

6.1.0's wheels are compiled with pyo3 0.28.2, which has two advisories fixed in 0.29.0:

  • High: out-of-bounds read in nth / nth_back for PyList / PyTuple iterators.
  • Medium: missing Sync bound on PyCFunction::new_closure closures.

epaper-dithering 6.1.1 rebuilds the wheels with pyo3 0.29.3, with no API changes (OpenDisplay/epaper-dithering#76).

What

  • pyproject.toml: epaper-dithering==6.1.0 → ==6.1.1.
  • uv.lock: only epaper-dithering changes.

Verification

1069 tests pass; ruff, mypy (strict) and pylint are clean.

As a fix(deps): commit, release-please will cut 7.18.1.

epaper-dithering 6.1.0's wheels are built with pyo3 0.28.2, which has two
advisories fixed in 0.29.0: an out-of-bounds read in PyList/PyTuple
iterator nth/nth_back (high) and a missing Sync bound on
PyCFunction::new_closure (medium). 6.1.1 rebuilds the wheels with pyo3
0.29.3; no API changes.

The pin is exact, so users (including Home Assistant) only get the patched
wheels through this bump.
@codecov

codecov Bot commented Oct 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@g4bri3lDev
g4bri3lDev merged commit 419bb91 into main Oct 7, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant