pg-boss changelog

Changelog History

Page 6

• v2.3.1 Changes

  • Patch to fix typescript types path

• v2.3.0 Changes

  • Typescript defs

• v2.2.0 Changes

  • Patched pg driver to 7.1

• v2.1.0 Changes

  • ⬆️ Upgrade pg driver to 7.0

• v2.0.0 Changes

  • ➕ Added state transition jobs and api for orchestration/saga support.
  • ➕ Added job fetch batching

• v1.1.0 Changes

  • ➕ Added onExpire(jobName, callback) for guaranteed handling of expiration (not just an event anymore)
  • 👷 failed was added as a job status
  • now emits 'failed' on unhandled subscriber errors instead of 'error', which is far safer
  • 👍 done() in suscribe() callbacks now support passing an error (the popular node convention) to 👷 automatically mark the job as failed as well as emitting failed. For example, 👷 if you are processing a job and you want to explicitly mark it as failed, you can just call done(error) at any time.
  • 👷 fail(jobId) added for external failure reporting along with fetch() and complete()
  • 👷 unsubscribe(jobName) added to undo a subscribe()

• v1.0.0 Changes

  • ⬇️ Dropped support for node 0.10 and 0.12
  • ➕ Added new publish option called singletonKey was added in order to make sure only 1 job of a certain type is active, queued or in a retry state
  • ➕ Added new publish option called singletonNextSlot was added in order to make sure a job is processed eventually, even if it was throttled down (not accepted). Basically, this is debouncing with a lousy name, because I'm not very good at naming things and didn't realize it at time
  • ➕ Added newJobCheckInterval and newJobCheckIntervalSeconds to subscribe() instead of just in the constructor
  • ➕ Added poolSize constructor option to explicitly control the maximum number of connections that can be used against the specified database
  • 👷 0.x had a data management bug which caused expired jobs to not be archived and remain in the job table. 👷 I also added a fix to the migration script so if you had any old expired jobs they should be automatically archived.
  • Error handling in subscriber functions! Previously I've encouraged folks to handle their own errors with try catch and be as defensive as possible in callback functions passed to subscribe(). However, it was too easy to miss that at times and if an error occurred that wasn't caught, 👷 it had the pretty lousy side effect of halting all job processing. 1.0.0 now wraps all subscriber functions in try catch blocks and emits the 'error' event if one is encountered.

• « First
• ‹ Prev
• 2
• 3
• 4
• 5
• 6