Bump celery from 0.4.0-rc4 to 0.4.0-rcn.11

[dependabot]

Bumps celery from 0.4.0-rc4 to 0.4.0-rcn.11.

Release notes

Sourced from celery's releases.

v0.4.0-rcn.11

What's new

Fixed ✅

• Fixed SemVer ordering.

Commits

0ab57af derive Serialize, Deserialize for TaskError (#274) 18ae003 Update serde-pickle requirement from 0.6 to 1.1 (#272) 341de2f style: correct typos (#273) d1d68fb (scripts/brokers): bind brokers to localhost only (#270) ab24e06 Bump mypy from 0.812 to 0.910 (#249) 4d9e035 Bump black from 21.5b0 to 21.9b0 (#268)

v0.4.0-rc10

What's new

Fixed ✅

• Fixed another bug with the app! and beat! related to issue #250.

Commits

2b395cf fix

v0.4.0-rc8

What's new

Changed ⚠️

• ⚠️ BREAKING CHANGE ⚠️

  The RegularSchedule in the beat module has been renamed to DeltaSchedule to be more coherent with Python Celery terminology, where it is sometimes called timedelta.

• Tokio updated to 1.0.0.

• The Broker::configure_task_routes produces BrokerError instead of CeleryError.

• The beat macro now expects a list of tasks that is used to initialize the scheduler.

• Errors have been refactored:

  • The BadRoutingPattern variant has been moved from CeleryError to BrokerError;
  • The CronScheduleError has been replaced by a ScheduleError enum with a CronScheduleError variant;
  • A ScheduleError variant has been added to BeatError
  • A BadRoutingPattern error has been added.

Added 🎉

• 🚀🚀 Redis broker support 🚀🚀
• Added the max_sleep_duration property on the Beat which can be used to ensure that the scheduler backend is called regularly (which may be necessary for custom backends).

... (truncated)

Changelog

Sourced from celery's changelog.

v0.4.0-rcn.11 - 2021-10-07

Fixed

• Fixed SemVer ordering.

v0.4.0-rc10 - 2021-08-30

Fixed

• Fixed another bug with the app! and beat! related to issue #250.

v0.4.0-rc8 - 2021-08-05

Changed

• ⚠️ BREAKING CHANGE ⚠️

  The RegularSchedule in the beat module has been renamed to DeltaSchedule to be more coherent with Python Celery terminology, where it is sometimes called timedelta.

• Tokio updated to 1.0.0.

• The Broker::configure_task_routes produces BrokerError instead of CeleryError.

• The beat macro now expects a list of tasks that is used to initialize the scheduler.

• Errors have been refactored:

  • The BadRoutingPattern variant has been moved from CeleryError to BrokerError;
  • The CronScheduleError has been replaced by a ScheduleError enum with a CronScheduleError variant;
  • A ScheduleError variant has been added to BeatError
  • A BadRoutingPattern error has been added.

Added

• 🚀🚀 Redis broker support 🚀🚀
• Added the max_sleep_duration property on the Beat which can be used to ensure that the scheduler backend is called regularly (which may be necessary for custom backends).
• Added a method Beat::schedule_named_task to add a scheduled task with a custom name.
• Added a method Broker::cancel to cancel an existing consumer.
• Changed Ok variant type of the the return type of Broker::consume. This is now a tuple that includes a unique consumer tag that can then be passed to Broker::cancel to cancel the corresponding consumer.
• Added a "coverage" job to GitHub Actions.
• Completed MessageBuilder struct

Fixed

• Fixed a bug with AMQPBroker::close() that would result in an error with lapin.
• Fixed a bug with the celery::app! macro that caused it to fail to compile when the broker connection string was passed as a variable instead of an expression.

v0.4.0-rc5 - 2020-11-19

Added

... (truncated)

Commits

• a7ddb20 (cargo-release) v0.4.0-rcn.11
• 0ab57af derive Serialize, Deserialize for TaskError (#274)
• 18ae003 Update serde-pickle requirement from 0.6 to 1.1 (#272)
• 341de2f style: correct typos (#273)
• d1d68fb (scripts/brokers): bind brokers to localhost only (#270)
• ab24e06 Bump mypy from 0.812 to 0.910 (#249)
• 4d9e035 Bump black from 21.5b0 to 21.9b0 (#268)
• 4a71979 (cargo-release) v0.4.0-rc10
• 2b395cf fix
• 904b69f (cargo-release) v0.4.0-rc9
• 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 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)