Update prefect to >=2.0.0,<2.16.2 🤖

[dependabot]

Updates the requirements on prefect to permit the latest version.

Release notes

Sourced from prefect's releases.

Release 2.16.1

Enhanced multiple schedule support 📅

prefect.yaml now supports specifying multiple schedules via the schedules key.

This allows you to define multiple schedules for a single deployment, and each schedule can have its own cron, interval, or rrule configuration:

 ...
 schedules:
    - cron: "0 0 * * *"
      active: false
    - interval: 3600
      active: true
    - rrule: "FREQ=YEARLY"
      active: true

In addition you can specify multiple schedules via arguments to prefect deploy:

prefect deploy ... --cron '4 * * * *' --cron '1 * * * *' --rrule 'FREQ=DAILY'

We've also added support for multiple schedules to flow.serve, flow.deploy and prefect.runner.serve. You can provide multiple schedules by passing a list to the cron, interval, or rrule arguments:

import datetime
import random
from prefect import flow
@​flow
def trees():
tree = random.choice(["🌳", "🌴", "🌲", "🌵"])
print(f"Here's a happy little tree: {tree}")
if name == "main":
trees.serve(
name="trees",
interval=[3600, 7200, 14400],
)

This will create a deployment with three schedules, one that runs every hour, one that runs every two hours, and one that runs every four hours. For more advanced cases, use the schedules argument.

</tr></table> 

... (truncated)

Changelog

Sourced from prefect's changelog.

Release 2.16.1

Enhanced multiple schedule support

prefect.yaml now supports specifying multiple schedules via the schedules key. This allows you to define multiple schedules for a single deployment, and each schedule can have its own cron, interval, or rrule configuration:

 ...
 schedules:
    - cron: "0 0 * * *"
      active: false
    - interval: 3600
      active: true
    - rrule: "FREQ=YEARLY"
      active: true

In addition, you can now specify multiple schedules via arguments to prefect deploy:

prefect deploy ... --cron '4 * * * *' --cron '1 * * * *' --rrule 'FREQ=DAILY'

We've also added support for multiple schedules to flow.serve, flow.deploy and prefect.runner.serve. You can provide multiple schedules by passing a list to the cron, interval, or rrule arguments:

import datetime
import random
from prefect import flow
@​flow
def trees():
tree = random.choice(["🌳", "🌴", "🌲", "🌵"])
print(f"Here's a happy little tree: {tree}")
if name == "main":
trees.serve(
name="trees",
interval=[3600, 7200, 14400],
)

This will create a deployment with three schedules, one that runs every hour, one that runs every two hours, and one that runs every four hours. For more advanced cases, use the schedules argument.

    trees.serve(
        name="trees",
        schedules=[
            IntervalSchedule(interval=datetime.timedelta(minutes=30)),
            {"schedule": RRuleSchedule(rrule="FREQ=YEARLY"), "active": True},
</tr></table> 

... (truncated)

Commits

• 2e3343b release notes for 2.16.1 (#12120)
• 1aa0fc2 Update @​prefecthq/vue-compositions to version 1.10.0 (#12125)
• e297260 Add a --replace option to "schedule create" command (#12123)
• 6dcd3f4 Add support for multiple schedules to prefect deploy (#12121)
• 93d6cc3 Fix a docstring (#12117)
• a28d1f5 ensure only scheduled runs can be marked late (#12113)
• 72369f3 allow 500s on docker test flake (#12114)
• d81abf3 Update flow.serve to support multiple schedules (#12107)
• 7e65c14 Update @​prefecthq/vue-compositions to version 1.9.0 (#12111)
• e269ac7 Fix schedule instructions for "prefect deploy"
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)