2.0.0b5

We're still in the process of evaluating changes to the Django integration. For stability it's advised to wait for a stable release (...duh). Of course, volunteers for testing in the beta are highly appreciated. Contact us through here.

Migrations

None

What's Changed

Bug Fixes

• Add explicit error message if users use the django app before .ready() by @ewjoachim in #955

Miscellaneous

• Update PULL_REQUEST_TEMPLATE.md by @ewjoachim in #954

Documentation

• Fix doc (wrong method) by @ewjoachim in #953

Full Changelog: 2.0.0b4...2.0.0b5

2.0.0b4

We're still in the process of evaluating changes to the Django integration. For stability it's advised to wait for a stable release (...duh). Of course, volunteers for testing in the beta are highly appreciated. Contact us through here.

Migrations

None

What's Changed

Bug Fixes

• Fix import in Django connector by @ewjoachim in #950

Full Changelog: 2.0.0b3...2.0.0b4

2.0.0b3

We're still in the process of evaluating changes to the Django integration. For stability it's advised to wait for a stable release (...duh). Of course, volunteers for testing in the beta are highly appreciated. Contact us through here.

Migrations

None

What's Changed

Bug Fixes

• DjangoConnector.get_worker_connector() uses psycopg3 if available by @ewjoachim in #946

Miscellaneous

• Django demo uses transaction.atomic() by @ewjoachim in #945

Full Changelog: 2.0.0b2...2.0.0b3

2.0.0b2

We're still in the process of evaluating changes to the Django integration. For stability it's advised to wait for a stable release (...duh). Of course, volunteers for testing in the beta are highly appreciated.

Migrations

No SQL migrations. There's a Django migration, which you can run safely as it doesn't contain any actual SQL code (you can also run it with --fake for the same result)

What's Changed

Features

• Periodic decorator is now on Blueprints by @ewjoachim in #918
• Add missing model and simplify launching Worker from Django by @ewjoachim in #919
• Django: PROCRASTINATE_ON_APP_READY by @ewjoachim in #921

Miscellaneous

• Add static migrations by @ewjoachim in #941

Docs

• django: small doc details by @ewjoachim in #910
• Add missing Django doc paragraph by @ewjoachim in #920
• Fix doc by @ewjoachim in #922
• Update max_delay description by @sebastien-mcrae in #924
• Fix README by @ewjoachim in #912

New Contributors

• @sebastien-mcrae made their first contribution in #924

Full Changelog: 2.0.0b1...2.0.0b2

2.0.0b1

This release refactors the Django integration completely. Head to the Django section in the doc to discover how it works.

Here's a summary of the changes:

• When using Procrastinate with Django, you don't need to define a Procrastinate App anymore. As long as Procrastinate is in your INSTALLED_APPS, you can use procrastinate.contrib.django.app. This special app uses the Django connection and doesn't need opening or closing.
• Tasks defined under the tasks submodule of any app in INSTALLED_APPS are loaded by default. This is configurable (you can add paths to load, or change the name of the module containing your tasks in every app)
• Some settings can be defined as PROCRASTINATE_* in your Django settings. See the complete doc for details (but there are no mandatory settings)
• You can run the CLI with ./manage.py procrastinate (if you use that, you won't have to configure an App either)
• Procrastinate now exposes 2 models and the corresponding ModelAdmins in your Django Admin. Those models are read-only. The Admin panels are very very basic for now.
• Procrastinate is tested with Django tasks that call the classic django ORM and the new async ORM methods.

What's Changed

Breaking changes

• Much better Django integration, implemented in #906

Kudos

While Procrastinate is mainly developed by myself, multiple contributors helped shaping this release over the last 2 years that it's been slowly boiling:

• @michaszcz for the original Django Connector PR, and @wgordon17, @mecampbellsoup, @adriangb for helpful comments
• @ignaciocabeza, and especially @turicas in #363 for submitting clear and actionable design directions that were very useful in deciding how to do this
• @paulzakin and @ponas for sharing ideas & feedback over on Discord (by the way, we now have a Discord server)

Full Changelog: 1.1.2...2.0.0

1.1.2

Migrations:

• https://github.com/procrastinate-org/procrastinate/blob/main/procrastinate/sql/migrations/01.01.01_01_job_id_bigint.sql
  Switches integer to bigint in procedure signatures (useful if you have more than 2B tasks)

What's Changed

Bug Fixes

• Switch remaining integer job_id elements to bigint, reported by @Vladimir-Filimonov via #902
• Aiopg: pass original kwargs to psycopg2, reported by @amacfie-tc via #909

Miscellaneous

• Switch doc to Markdown by @ewjoachim in #904
• Fix badges by @ewjoachim in #905

Full Changelog: 1.1.1...1.1.2

1.1.1

Migrations

None

What's Changed

Bugfixes

• Worker: install_signal_handlers=True/False by @ewjoachim / @sevaho in #894

Miscellaneous

• Update badges by @ewjoachim in #900

Full Changelog: 1.1.0...1.1.1

1.1.0

Migrations

Yes ! For the first time in a while, there are migrations. They're mainly dropping old functions now that we're in 1.0, following our migration doc. As a reminder, you should apply the migrations listed for 1.0 (such as the one below) before you upgrade to 1.1.

• https://github.com/procrastinate-org/procrastinate/blob/main/procrastinate/sql/migrations/01.00.00_01_remove_old_finish_job_function.sql

What's Changed

Miscellaneous

• Apply future migrations following the release of 1.0 by @ewjoachim in #893

Dependencies

• Upgrade to upload-artifact@v4 by @ewjoachim in #891

Misc

• Update pr-labels.yml by @ewjoachim in #892

Full Changelog: 1.0.3...1.1.0

1.0.3

Migrations

None

Miscellaneous

• Tentatively fix pypi release

1.0.2

Migrations

None

Miscellaneous

• Improve release management by @ewjoachim in #889
• Static type analysis with Pyright by @ewjoachim in #887

Full Changelog: 1.0.1...1.0.2