v0.22.0

What's Changed

• feat: fastify v5 support by @HW13 in #72
• feat: configurable spanOptions by @HW13 in #73

BREAKING CHANGES:

• minimum fastify version of 4.10.0 is now required

Full Changelog: v0.21.0...v0.22.0

v0.21.0

What's Changed

• feat: added new option propagateToReply by @10xLaCroixDrinker in #68

Full Changelog: v0.20.0...v0.21.0

v0.20.0

What's Changed

• feat: include hooks not within route handler when wrapping routes by @10xLaCroixDrinker in #65

New Contributors

• @tmcw made their first contribution in #64

Full Changelog: v0.19.0...v0.20.0

v0.19.0

What's Changed

• fix: wrapped route handlers were forced to be async or return a promise by @10xLaCroixDrinker in #62

Full Changelog: v0.18.0...v0.19.0

v0.18.0 Release

What's Changed

• chore: remove usage of serviceName by @HW13 in #53
• chore: update lint devDependencies by @HW13 in #55
• ci: add v18 to validate workflow's matrix.node by @HW13 in #54
• fix: use request.routeOptions instead of deprecated request.routerPath by @10xLaCroixDrinker in #60
• Use more compatible default export ts syntax by @asakusuma in #59
• chore: fix failing type tests by @HW13 in #61

New Contributors

• @10xLaCroixDrinker made their first contribution in #60
• @asakusuma made their first contribution in #59

Full Changelog: v0.17.1...v0.18.0

v0.17.1 Release

Fixes

• fix: upgrade to fastify-plugin@^4.0.0 (#51)

v0.17.0 Release

Enhancements

• chore(fastify): upgrade fastify to 4.x (#47)

Breaking Changes

• Drop support of Node v12
• Fastify v4 required now

v0.16.0 Release

Enhancements

• fix!: use low-cardinality span name and remove serviceName option (#41)

Breaking Changes

• formatSpanName function now only receives Fastify request object.

  (request) => `My Span Name - ${request.id}`

v0.15.0 Release

Enhancements

• feat: Allow opts.ignoreRoutes to accept a function (#39)

v0.14.0 Release

Enhancements

• feat: update to opentelemetry/api 1.0.0 (#37 )

Breaking Changes

• Implementations depending on previous versions of @opentelemetry/api may have compatibility issues. Ensure that your app/module as well as its dependencies (such as @opentelemetry/node and @opentelemetry/core) are all using @opentelemetry/api v1.0.0. See the OpenTelemetry/API upgrade guidelines here.