[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pyee	==13.0.1 → ==14.0.0

---

Release Notes

jfhbrook/pyee (pyee)

v14.0.0

Compare Source

• Use uv instead of pip-tools
• Move dev extras to dev dependency group
• Drop support for Python 3.8, 3.9, 3.10 and 3.11
• BUGFIX: Remove all listeners only for specified event

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[e2jk]

This is currently blocked, not just failing: playwright==1.62.0 (the latest release on PyPI) pins pyee<14,>=13, so pip's resolver can't satisfy both that and this PR's pyee==14.0.0 bump — see the failing CI run.

There's no newer playwright release to bump alongside it yet, so this can't be fixed by rebasing or retrying — it needs playwright itself to release a version compatible with pyee 14.x first. Leaving this PR open rather than closing it, since closing suppresses future reminders for this exact version per Renovate's own policy. Once playwright updates (tracked as its own PR, e.g. #158 previously), this PR should naturally pick up a compatible pyee resolution on its next rebase.

I've added the no-auto-rebase label so our stale-PR auto-rebase workflow skips this one instead of burning its retry attempts on something rebasing can't fix (see docs/development.md's "Landing changes on main" section once merged).

[e2jk]

Blocked by playwright==1.62.0 (pinned in requirements/ci.txt), which still requires an older pyee and conflicts with this bump to 14.0.0:

ERROR: Cannot install -r requirements/ci.txt (line 701) and pyee==14.0.0 because these package versions have conflicting dependencies.

For a quick manual check of whether a newer playwright release has picked up pyee>=14 support:

• https://pypi.org/project/playwright/ — latest published version at a glance
• https://github.com/microsoft/playwright-python/releases — changelog, to confirm the pyee bump specifically

Once playwright supports pyee 14.x, this should rebase and resolve cleanly.

[e2jk]

FYI I submitted microsoft/playwright-python#3208 about relaxing the upper bound of the dependency.

[e2jk]

microsoft/playwright-python#3208 has been addressed by microsoft/playwright-python#3218 , now wait for a new upstream release and then wait on the 14 days cooldown period.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

[e2jk]

Superseded by #393, which bumped playwright to 1.64.1 (including the upstream fix from microsoft/playwright-python#3218, relaxing the pyee pin to >=13,<15) together with pyee 14.0.0.