Skip to content

chore(deps): update python packages#234

Open
sassanix wants to merge 1 commit into
mainfrom
renovate/python-packages
Open

chore(deps): update python packages#234
sassanix wants to merge 1 commit into
mainfrom
renovate/python-packages

Conversation

@sassanix

@sassanix sassanix commented May 25, 2026

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Update Change OpenSSF
APScheduler (changelog) patch ==3.11.2 β†’ ==3.11.3 OpenSSF Scorecard
PyJWT minor ==2.12.1 β†’ ==2.13.0 OpenSSF Scorecard
apprise minor ==1.10.0 β†’ ==1.11.0 OpenSSF Scorecard

Release Notes

agronholm/apscheduler (APScheduler)

v3.11.3

Compare Source

  • Fixed sub-minute interval jobs stalling for the duration of a DST spring-forward gap when the scheduler was configured with a ZoneInfo time zone, caused by the wakeup delay being computed from the naive wall-clock difference instead of the actual UTC difference (#​1103)
  • Fixed imported jobs missing their scheduler and job store links (#​1119)
jpadilla/pyjwt (PyJWT)

v2.13.0

Compare Source

caronc/apprise (apprise)

v1.11.0

Compare Source

What's Changed

A big win for this release is priortization of grouped/tagged content. Basically, this release allows you to tag multiple items and provide a weight to them. Apprise will attempt to notify the highest priority/weighted services first (of same level), and only if this level fails will it try the next. Tagging is no longer just a tag. It's now weight:tag too; for example 100:friends associates the weight of 100 with the tag friends. You can still continue to notify friends with your Apprise calls, but if there are weight categories, then these will be factored into the order. Highest priority (weighted) tags have a lower integer value (zero being the higest priority). Only the next priority will be notified if the first fails.

This releae also allows you to set up a notifiation service to gracefully fail and not have Apprise itself report a failure. This is useful for situations where you notify several end points and you really don't care if they're unavailable or not. Apprise wil do it's usual best effort to send the notification, but not treat it as a failure if it can't get through. Use optional=yes on your Apprise URL.

Thirdly, this release introduces retries! You can now have Apprise attempt to notify your endpoint a second, or a third, (up to 10x) tries before giving up and deeming it unable to send the notification. Use retry=X on your Apprise URL

πŸ“£ New Notification Services:
🐞 Bugfixes
  • improved robustness of windows test cases preventing others from passing in #​1609
  • Handle XMPP SASL SCRAM-PLUS / Channel Binding in #​1619
  • TRACE logging during apprise init cleaned up in #​1622
  • fixed mastodon error: AttributeError - 'list' object has no attribute 'union' in #​1631
πŸ’‘ Features
❀️ Life-Cycle Support

Installation

Apprise is available on PyPI through pip:

# Install Apprise v1.11.0 from PyPI
pip install apprise==1.11.0

Full Changelog: caronc/apprise@v1.10.0...v1.11.0


Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

πŸ‘» Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@sassanix sassanix force-pushed the renovate/python-packages branch from 89c7759 to 814b300 Compare June 1, 2026 04:05
@sassanix sassanix changed the title chore(deps): update dependency pyjwt to v2.13.0 (from 2.12.1) chore(deps): update python packages Jun 1, 2026
@sassanix sassanix force-pushed the renovate/python-packages branch from 814b300 to 618579a Compare June 29, 2026 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants