Repository navigation
chore(deps): update dependency croniter to v7 - #794
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
renovate
Bot
force-pushed
the
renovate/croniter-7.x
branch
17 times, most recently
from
November 18, 2026 12:38
178637a to
20c15ad
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/croniter-7.x
branch
from
November 18, 2026 16:49
20c15ad to
87cbd7a
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:
==6.2.4→==7.0.0Release Notes
pallets-eco/croniter (croniter)
v7.0.0Compare Source
This is a major release because several bug fixes change what existing, valid
expressions mean. Read Upgrading to 7.0 before you upgrade. Every change is
listed in full under Bugfixes.
Upgrading to 7.0
expand_from_start_timeactually means — that it moves the phase of acycle and not the values a field may take, that every field re-bases including the
optional seconds and years, and that the phase is read in the start time's own
timezone. Also document that a range with two equal bounds (
Jan-Jan,Sun-Sun)means the whole cycle rather than the value it names, which was undocumented and is
the rule behind several of the bugs fixed in this release. [#257, @potiuk]
expand_from_start_time: that a field declaring its ownrange keeps both bounds and only the phase moves, that moving a phase inside a fixed
window can cost one period, that an expression whose phase does not fit is honoured as
written, and that a wrapping range is left alone. [#255, @potiuk]
Packaging
fd13d2e, #240;5cd2e46, #238]Configuration
📅 Schedule: (in timezone America/Los_Angeles)
* * * * 0,6)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.