Skip to content

chore(deps): update dependency pyee to v14 - #199

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pyee-14.x
Open

chore(deps): update dependency pyee to v14#199
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pyee-14.x

Conversation

@renovate

@renovate renovate Bot commented Aug 27, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

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.

@renovate
renovate Bot requested a review from e2jk as a code owner August 27, 2026 04:47
@e2jk e2jk added the no-auto-rebase Blocked on something external (e.g. an upstream release) -- don't auto-rebase label Aug 27, 2026
@e2jk

e2jk commented Aug 27, 2026

Copy link
Copy Markdown
Owner

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 added a commit that referenced this pull request Aug 27, 2026
@e2jk
ci: let auto-rebase-stale-bot-prs skip PRs labelled no-auto-rebase
7c8a528 
PR #199 (pyee 13.0.1 → 14.0.0) is stale-by-coincidence (BEHIND main) but
can't actually be fixed by rebasing — playwright==1.62.0 (the latest
release) pins pyee<14,>=13, so the bump only becomes valid once playwright
itself releases a compatible version. Without this, the cron would burn
all 3 rebase attempts on a PR that can never pass, then go silent instead
of staying visibly blocked.

Documents the mechanism in docs/development.md alongside the existing
"Landing changes on main" explanation of why bot PRs go stale in the
first place.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@e2jk e2jk Awaiting requested review from e2jk e2jk is a code owner

Assignees

No one assigned

Labels

no-auto-rebase Blocked on something external (e.g. an upstream release) -- don't auto-rebase

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@e2jk