Bump celery from 0.4.0-rc4 to 0.4.0-rc5

[dependabot]

Bumps celery from 0.4.0-rc4 to 0.4.0-rc5.

Release notes

Sourced from celery's releases.

v0.4.0-rc5

What's new

Added 🎉

• Added the CronSchedule struct to support Celery's crontab schedules.

Changed ⚠️

• ⚠️ BREAKING CHANGE ⚠️

  To improve the app! and beat! macros and accomodate custom Brokers and SchedulerBackends, we've had to make breaking changes to the way these macros are invoked.

  The biggest change is that the macros now return a future of Result<Celery> or Result<Beat>. This means you must now call .await? on the return value of the macro.

  The other change is that you must now supply the actual Broker type. Previously, you could write something like broker = AMQP { "amqp://my-broker-url" }, but now you have to write it like broker = celery::broker::AMQPBroker { "amqp://my-broker-url" }.

  For a concrete example of these changes, the old way looked like this:

  #[tokio::main]
  async fn main() -> anyhow::Result<()> {
      let app = celery::app!(
          broker = AMQP { "amqp://my-broker-url" },
          tasks = [add],
          task_routes = ["*" => "celery"],
      );
  // ...
  Ok(())
  
  }

  Whereas now that will look like this:

  #[tokio::main]
  async fn main() -> anyhow::Result<()> {
      let app = celery::app!(
          broker = celery::broker::AMQPBroker { "amqp://my-broker-url" },
          tasks = [add],
          task_routes = ["*" => "celery"],
      ).await?;

... (truncated)

Changelog

Sourced from celery's changelog.

v0.4.0-rc5 - 2020-11-19

Added

• Added the CronSchedule struct to support Celery's crontab schedules.

Changed

• ⚠️ BREAKING CHANGE ⚠️

  To improve the app! and beat! macros and accomodate custom Brokers and SchedulerBackends, we've had to make breaking changes to the way these macros are invoked.

  The biggest change is that the macros now return a future of Result<Celery> or Result<Beat>. This means you must now call .await? on the return value of the macro.

  The other change is that you must now supply the actual Broker type. Previously, you could write something like broker = AMQP { "amqp://my-broker-url" }, but now you have to write it like broker = celery::broker::AMQPBroker { "amqp://my-broker-url" }.

  For a concrete example of these changes, the old way looked like this:

  #[tokio::main]
  async fn main() -> anyhow::Result<()> {
      let app = celery::app!(
          broker = AMQP { "amqp://my-broker-url" },
          tasks = [add],
          task_routes = ["*" => "celery"],
      );
  // ...
  Ok(())
  
  }

  Whereas now that will look like this:

  #[tokio::main]
  async fn main() -> anyhow::Result<()> {
      let app = celery::app!(
          broker = celery::broker::AMQPBroker { "amqp://my-broker-url" },
          tasks = [add],
          task_routes = ["*" => "celery"],
      ).await?;

... (truncated)

Commits

• 4ef0df8 (cargo-release)
• 6f284d1 Changes to app creation API (#195)
• 82bcb2c Add support for cron schedules (#200)
• bcdd4d2 Fix a bug which caused a delayed task to be dropped without being executed (#...
• 3a757d7 Update env_logger requirement from 0.7 to 0.8 (#197)
• 1ff318c update README and examples (#193)
• 3a53179 Bump mypy from 0.782 to 0.790 (#192)
• e85cfcb ensure cache refreshed every week to avoid stale bloat (#191)
• da9eaaa use intradoc links (#190)
• 4aebecd use new way of setting env vars in GH Actions (#189)
• 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)

[dependabot]

Superseded by #47.