bensheldon/good_job v2.0.0

on GitHub

Changelog

Upgrading v1 to v2

GoodJob v2 introduces a new Advisory Lock key format that is different than the v1 advisory lock key format; it's therefore necessary to perform a simple, but staged production upgrade. If you are already using >= v1.12+ no other changes are necessary.

1. Upgrade your production environment to v1.99.x following the minor version upgrade process, including database migrations. v1.99 is a transitional release that is safely compatible with both v1.x and v2.0.0 because it uses both v1- and v2-formatted advisory locks.
2. Address any deprecation warnings generated by v1.99.
3. Upgrade your production environment to v1.99.x to v2.0.x again following the minor upgrade process.

Notable changes:**

• Renames :async_server execution mode to :async; renames prior :async execution mode to :async_all.
• Sets default Development environment's execution mode to :async with disabled polling.
• Excludes performing jobs from enqueue_limit's count in GoodJob::ActiveJobExtensions::Concurrency.
• Triggers GoodJob.on_thread_error for unhandled ActiveJob exceptions.
• Renames GoodJob.reperform_jobs_on_standard_error accessor to GoodJob.retry_on_unhandled_error.
• Renames GoodJob::Adapter.shutdown(wait:) argument to GoodJob::Adapter.shutdown(timeout:).
• Changes Advisory Lock key format from good_jobs[ROW_ID] to good_jobs-[ACTIVE_JOB_ID].
• Expects presence of columns good_jobs.active_job_id, good_jobs.concurrency_key, good_jobs.concurrency_key, and good_jobs.retried_good_job_id.