8000 chore(deps): bump croniter from 6.2.4 to 7.0.0 by dependabot[bot] · Pull Request #10 · gemini960114/HostSpark · GitHub
[go: up one dir, main page]

Skip to content

chore(deps): bump croniter from 6.2.4 to 7.0.0 - #10

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/croniter-7.0.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/croniter-7.0.0

Conversation

@dependabot
@dependabot dependabot Bot commented on behalf of github Nov 15, 2026
Copy link
Copy Markdown

Bumps croniter from 6.2.4 to 7.0.0.

Release notes

Sourced from croniter's releases.

7.0.0

What's Changed

New Contributors

Full Changelog: pallets-eco/croniter@6.2.4...7.0.0

Changelog

Sourced from croniter's changelog.

7.0.0 (2026-11-08)

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


Changes 1 and 2 are silent: nothing fails, schedules just fire at different times.
Changes 3 and 4 raise an exception.

1. A step that starts at the field maximum now means one value, not the whole field (#246). Each field's maximum is 59 for seconds and minutes, 23 for hours, 31 for day-of-month, 12/DEC for month, 6/SAT (or 7) for day-of-week and 2099 for years.

  • Who is affected: any expression in which a field starts with its maximum followed by /, for example 59/15, 23/6, 31/5, DEC/3, SAT/2, 6/1 or 2099/1.

  • What to do: find these expressions in your code, configuration and stored data. A field value such as 59/... or 6/... is the pattern to look for. Decide what each one was meant to do:

    • It meant "every": replace it with * or */{step}. * * * * 6/1 becomes * * * * *, and 59/15 * * * * becomes */15 * * * *.
    • It meant "only the maximum": no change is needed, because 7.0 now does that.
    • It is in a year field (2099/1) or on a day that can be missing (31/5 with month 2): the expression may now have no future match and raise CroniterBadDateError (see 4 below). Rewrite it with *.

2. expand_from_start_time=True keeps the bounds of ranges (#255, #256, #246). If you never pass expand_from_start_time, skip this item: default-mode schedules are unchanged.

  • Who is affected: expressions with an explicit range, an equal range such as 1-1/3, a wrapping range such as 6-0, or a stepped start such as 5/15. In 6.x such a range could fire outside its own bounds, so * 8-17 * * * fired at hours 0-17. The phase was also read in UTC instead of the start time's own time zone.

  • What to do: for each schedule that uses the flag, compare the old and new expanded values. Install 7.0 in a separate environment, or run the snippet below under both versions with your own expressions, start times and time zones:

    .. code-block:: python

    from datetime import datetime, timezone
    from croniter import croniter
    

</tr></table>

... (truncated)

Commits
  • 2884eac Release as 7.0.0 and add an upgrade guide (#294)
  • 53ecf5c Prepare for release 6.3.0 (#293)
  • 1b0c241 Remove the docker images builder workflow (#292)
  • 54ef862 Do not report a gap-shifted DST alternative as a fire time (#266)
  • 80f9c79 reject H(a-b)/R(a-b) ranges whose bounds lie outside the field (#289)
  • c2f4cdf Require max_years_between_matches to be an int >= 1 or None (#272)
  • b4c7661 Bump hatchling from 1.32.4 to 1.33.0 in the pip-dependencies group (#291)
  • 2725ef5 Bump the github-actions group with 2 updates (#290)
  • 284d013 reject non-ASCII whitespace between cron fields (#288)
  • 7fa4abb reject out-of-range nth day-of-week in _expand without assert (#278)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [croniter](https://github.com/pallets-eco/croniter) from 6.2.4 to 7.0.0.
- [Release notes](https://github.com/pallets-eco/croniter/releases)
- [Changelog](https://github.com/pallets-eco/croniter/blob/main/CHANGELOG.rst)
- [Commits](pallets-eco/croniter@6.2.4...7.0.0)

---
updated-dependencies:
- dependency-name: croniter
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants

0