Skip to content

chore(deps): bump pywebpush from 2.3.0 to 2.5.0 in /backend with regenerated lockfiles - #295

Merged
d3mocide merged 1 commit into
mainfrom
chore/pywebpush-2.5.0
Sep 16, 2026
Merged

d3mocide merged 1 commit into
mainfrom
chore/pywebpush-2.5.0

Conversation

@d3mocide

Copy link
Copy Markdown
Owner

Supersedes #283.

Why this PR exists

#283 only changed backend/pyproject.toml (the dependabot default), which doesn't regenerate the lockfiles. Since CI installs --require-hashes from the lock, the pin would never take effect — and it now fails the lockfile-drift check added in #292 (Lockfiles are out of sync with pyproject.toml).

This PR carries the same bump with both lockfiles regenerated.

What it does

Bump
pywebpush 2.3.0 → 2.5.0

No transitive dependency changed beyond pywebpush's own.

Testing

Clean Python 3.12 venv, installed exactly as CI does:

  • pip-audit — No known vulnerabilities found
  • ruff check . — All checks passed
  • mypy luma --ignore-missing-imports — Success, 78 source files
  • pytest -x -q — 201 passed
  • Lockfiles idempotent under a plain pip-compile re-run

Once this is green, #283 can be closed as superseded.

🤖 Generated with Claude Code

https://claude.ai/code/session_013NXCVFjazLiKnd8mCCCj7r


Generated by Claude Code

…iles

Supersedes #283, which only changed pyproject.toml and would fail
the lockfile-drift check added in #292.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013NXCVFjazLiKnd8mCCCj7r
@d3mocide
d3mocide marked this pull request as ready for review September 16, 2026 16:13
@d3mocide
d3mocide merged commit bccedeb into main Sep 16, 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.

2 participants