Releases: imTigger/laravel-job-status
Maintainance and Stability Update
Support instant JobStatus update within transaction
-
Dedicated database connection support is added.
Therefore JobStatus updates can be saved instantly even within your application transaction.
Read setup step 6 for instructions. -
Fixed errors caused by calling attempts() on null object, thanks @PatBriPerso
Support instant JobStatus update within transaction
Dedicated database connection support is added.
Therefore JobStatus updates can be saved instantly even within your application transaction.
Read setup step 6 for instructions.
Fixed path for migration
Credit to @tarekadam @PatBriPerso
First Major Release
- Added more tests
- Added TrackableJob interface
- Minimum requirements changed to php > 7.1 and Laravel 5.5
- Some refactor of update code
Thanks to @crashkonijn
Fixing Beanstalkd `attempts()` issues
Fixing Beanstalkd attempts()
issues
Thank you @alexking for the PR!
(Optional) Publish package migration into project migrations
Thank you @bagwaa for the PR!
Use Job's displayName() for type field if method exists
Use Job's displayName() for type field if method exists
Store "Label Generation Job" instead of "App\Jobs\LabelJob"
This change may break application if you have displayName() in your Job and have specific use case type
field
Therefore minor version bumped
Fixed: Array to string conversion exception when updating `job_statuses`
Fixed: Array to string conversion exception when updating job_statuses
Thank you @dverraes for the PR!
Fixed compatibility of Laravel 5.3
v0.1.13 Fixex compatibility with Laravel 5.3