chore(deps): update dependency apscheduler to ~=3.11.3 - #49
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/apscheduler-3.x
branch
from
December 22, 2025 02:59
ace4666 to
19dd957
Compare
renovate
Bot
force-pushed
the
renovate/apscheduler-3.x
branch
from
June 28, 2026 23:41
19dd957 to
d9b1de3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~=3.10.1→~=3.11.3Release Notes
agronholm/apscheduler (apscheduler)
v3.11.3Compare Source
ZoneInfotime zone, caused by the wakeup delay being computed from the naive wall-clock difference instead of the actual UTC difference (#1103)v3.11.2Compare Source
CronTriggerscheduled in a repeated time interval during DST transitions could cause the scheduler to get stuck in an infinite loop (#1021; PR by @soulofakuma)v3.11.1Compare Source
scheduler.shutdown()not raisingSchedulerNotRunning(or raising the wrong exception) for asynchronous schedulers when the scheduler is in fact not runningCronTriggersticking on a folded datetime during the fall-back DST transition (#1021 <#1021>_; PR by @berianjames)`v3.11.0Compare Source
ZoneInfotime zones and deprecated support for pytz time zonesCalendarIntervalTrigger, backported from the 4.x seriesscheduler.export_jobs()andscheduler.import_jobs(), respectivelysixProcessPoolExecutorto spawn new subprocesses from scratch instead of forking on all platformAsyncIOSchedulerinadvertently creating a defunct event loop at start, leading to the scheduler not working at allProcessPoolExecutornot respecting the passed keyword arguments when a broken pool was being replacedConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.