0.6.2

Bug Fixes

• koa: fix koa-websocket not working when the koa plugin is enabled (#346), fixes #341
• package: add npmignore to only include relevant files (#345), fixes #343

0.6.1

Bug Fixes

• graphql: fix graphql integration not working when using schema stitching (#323), fixes #235, #307
• graphql: fix resolver scope when configured with the depth option (#319)
• graphql: fix error when field depth is higher than the configured depth (#318)
• hapi: fix support for older versions (#296)
• koa: fix incorrect route (#303)

Improvements

• core: add logging for parent spans finished before their children (#320)
• core: add logging to the text map propagator (#305)

0.6.0

Bug Fixes

• core: fix distributed tracing compatibility of generated IDs (#279)
• core: fix already flushed traces being reused (#277)
• core: fix client sampling resulting in incorrect metrics (#276)
• express: fix repeated traces in some cases (#255)
• http: fix repeated traces on Node <9 when tracing https requests (#268), thanks @alloy!

Features

• amqp10: add amqp10 integration (#254)
• core: add support for sampling priority (#217), closes #208, thanks @stephenh and @alloy!
• core: add an option to enable/disable the tracer (#209)
• express: add option to record HTTP headers (#266), thanks @alloy!
• graphql: add support for subscriptions (#249), fixes #248, thanks @clayne11!
• graphql: add instrumentation for document parsing and validation (#245), thanks @alloy!
• graphql: add option to record variables (#245), thanks @alloy!
• hapi: add hapi integration (#282)
• ioredis: add ioredis integration (#291), closes #259
• koa: add koa integration (#288), closes #202
• memcached: add memcached integration (#290), closes #163
• pg: add support for pg 7.x (#250), thanks @archerabi!
• restify: add restify integration (#289)

Improvements

• core: improve performance of generating IDs (#279)
• deps: remove node-memwatch from optional dependencies (#281), closes #257
• deps: bump url-parse version to address vulnerability (#265), closes #264, thanks @benjamine!

0.5.6

Bug Fixes

• express: fix older express 4.x minor versions not instrumented properly (#243)
• express: fix possible race condition in express plugin (#239)
• express: fix missing path on errors in express plugin (#238)
• graphql: fix multiple executions with the same contextValue in graphql (#240)
• http: fix http plugin resuming the stream before it can be consumed (#244)
• mongodb-core: fix mongodb-core plugin not sanitizing buffers in resource name (#241)

0.5.5

Bug Fixes

• core: fix memory leak when using scopes with recursive timers (#227)
• express: fix express leaking scope on other requests when using task queues (#230)
• express: fix memory leak in express when used with recursive timers (#228)

0.5.4

Bug Fixes

• http: fix detection of aws signature when using array headers (#220), closes #219

0.5.3

Improvements

• core: flush pending traces when the process exits gracefully (#207)

Bug Fixes

• express: fix express not always propagating context to middleware (#214)
• express: fix express path being lost when active scope is closed (#212)
• http: fix memory leak in http plugin when sockets are reused (#210), closes #206
• http: fix 403 error from AWS when sending a signed request (#205)

0.5.2

Bug Fixes

• core: fix memory leak when destroy is called before after on context (#203), closes #197 #201

0.5.1

Bug Fixes

• core: fix reference to https plugin that no longer exists (#199), closes #198

0.5.0

General Availability

This release marks the end of our open beta and is the first officially supported version. 🎉

Bug Fixes

• core: fix span recorded multiple times if finish() is called more than once (#194)
• core: fix error when the tracer is bundled with the app (#191), thanks @InventingWithMonster!
• core: fix scope manager being instantiated multiple times (#188)
• express: fix express path being lost when changing scope (#193)
• pg: fix pg parent scope not available in query callbacks (#190)

Features

• plugins: update service names and span types to match the specification (#192)

Breaking Changes for Beta Users

This release changes the default service names of most integrations. While in most cases this should be seamless, it may require updating any other feature linked directly to the service name such as monitors. You may also opt to keep the previous name by explicitly setting them in the integration configuration