@@ -19,14 +19,19 @@ to make sure the system as a whole remains consistent.
1919Read more:
2020[ Worker Pro Migration] ( https://worker.graphile.org/docs/pro/migration ) .
2121
22- ## Pending
23-
24- - BREAKING: Jobs and queues are now ` locked_by ` their ` WorkerPool ` 's id rather
25- than the ` workerId ` . Be sure to upgrade
26- [ Worker Pro] ( https://worker.graphile.org/docs/pro ) at the same time if you're
27- using it!
28- - BREAKING: Graphile Worker Pro users will need to update to 0.2.x at the same
29- time as updating Graphile Worker.
22+ ## v0.17.0
23+
24+ Major performance enhancements in this release, but they're opt-in!
25+
26+ - BREAKING: jobs and queues are now ` locked_by ` their ` WorkerPool ` 's id rather
27+ than the ` workerId ` .
28+ - BREAKING: Worker Pro users need to update to ` @graphile-pro/worker@0.2.x ` at
29+ the same time as updating Graphile Worker to this release (due to the above
30+ breaking change).
31+ - BREAKING: We'll now warn you if you haven't installed error handlers on the
32+ pool, and will only install them ourself if needed.
33+ - BREAKING: Fixes bug where CLI defaults override ` graphile.config.js ` settings
34+ (by removing CLI defaults).
3035- New ** batching of job completion** can be enabled by setting
3136 ` preset.worker.completeJobBatchDelay ` and ` preset.worker.failJobBatchDelay ` to
3237 a number ` 0 ` or higher. This can significantly reduce load on the database, at
@@ -61,10 +66,6 @@ Read more:
6166 clearer that it's for use in one-off locations (some felt the "quick" referred
6267 to the speed it executed, rather than the amount of effort required from the
6368 programmer).
64- - We'll now warn you if you haven't installed error handlers on the pool, and
65- will only install them ourself if needed.
66- - Fixes bug where CLI defaults override ` graphile.config.js ` settings (by
67- removing CLI defaults).
6869- Fix bug where executable tasks had their stdout/stderr ignored; this is now
6970 output via logging (thanks @wineTGH ).
7071- Fix race condition when multiple workers attempt to initialise the database at
0 commit comments