All Versions
57
Latest Version
Avg Release Cycle
26 days
Latest Release
-
Changelog History
Page 2
Changelog History
Page 2
-
v5.0.8 Changes
August 20, 2020- ๐ท Retention policy applied to abandoned jobs in retry state.
- Cron monitoring properly disabled when archive interval is set lower than 1 minute.
-
v5.0.7 Changes
August 19, 2020- ๐ Fixed cron monitor interval.
-
v5.0.6 Changes
August 14, 2020- โ Added a cron monitor to verify the health of the cron queue.
-
v5.0.5 Changes
August 06, 2020- โ Removed latency offset calculation during clock skew detection. This was causing cron processing to be paused whenever a significant wait time was required to acquire a connection from the pool.
-
v5.0.4 Changes
- ๐ Fixed debouncing offset calculation which would sometimes cause an interval overlap. This was causing cron processing to be paused.
- ๐ Fixed debouncing offset calculation which would sometimes cause an interval overlap. This was causing cron processing to be paused.
-
v5.0.3 Changes
July 30, 2020โช Reintroduced archive delay for completed jobs to restore reliable throttling and debouncing.
publish()
will now throw if you use a throttling or debouncing interval set higher than the archive delay.- โ Added
archiveCompletedAfterSeconds
constructor option to allow overriding the default of 12 hours. If you set this lower than 60s, a warning will be emitted and cron processing will be disabled, as this feature relies on debouncing once a minute to operate properly. - ๐ Fixed maintenance queue monitoring bug introduced in 5.0.2
-
v5.0.2 Changes
July 29, 2020- โก๏ธ Updated queue maintenance monitoring to abort stalled active jobs
-
v5.0.1 Changes
July 16, 2020- Dependencies PR for lodash dep
-
v5.0.0 Changes
July 15, 2020โฑ The pg-boss team hired a timekeeper and now has distributed cron-based scheduling! This works across all instances based on the database server's time as a central clock.
New functions:
schedule(name, cron, data, options)
unschedule(name)
getSchedules()
New constructor configuration properties:
clockMonitorIntervalSeconds
clockMonitorIntervalMinutes
noScheduling
๐ Changes
- โฑ MAJOR: Removed
connect()
anddisconnect()
to simplify usage since these functions became obsolete in v4. If you had relied on secondary instances running withconnect()
, you should switch tostart()
. Sincestart()
is multi-master, it's safe to let it monitor and submit maintenance work, but if you need to opt out of this for whatever reason on a particular instance, set thenoSupervisor
andnoScheduling
constructor options totrue
. - ๐ฆ MAJOR: Dropped
poolSize
in constructor database config to standardize onmax
property used in the pg package. - ๐ MAJOR: Dropped Node 8 support and from Travis CI builds.
๐ง MAJOR: Adjusted maintenance configuration settings for clarity. For example, some operations run on an interval and contain the word "interval". However, other settings are time-based policies evaluated only after maintenance is run. These also contained "interval" which made it challenging to explain the differences between them.
- Removed properties related to moving completed jobs to the archive table. Completed jobs will be moved to the archive table based on the maintenance interval going forward.
Old New archiveIntervalSeconds
** REMOVED ** archiveIntervalMinutes
** REMOVED ** archiveIntervalHours
** REMOVED ** archiveIntervalDays
** REMOVED ** - Renamed properties for controlling when to delete jobs from the archive table
Old New deleteIntervalSeconds
deleteAfterSeconds
deleteIntervalMinutes
deleteAfterMinutes
deleteIntervalHours
deleteAfterHours
deleteIntervalDays
deleteAfterDays
-
v4.3.4 Changes
July 02, 2020- Typescript types fix for db connections. Includes PR from @mlegenhausen