Release v0.9.0

Changed

• WithFilter option now support multiple filter functions, just like in otelmux. (#47)
• Upgrade go.opentelemetry.io/otel, go.opentelemetry.io/otel/sdk, & go.opentelemetry.io/otel/trace to v1.28.0. (#49)
• Upgrade github.com/go-chi/chi/v5 to v5.1.0. (#49)
• Set the go versions for testing in both Makefile & compatibility-test.yml to 1.21 & 1.22. (#49)

Removed

• Drop support for Go <1.21. (#49)

Full Changelog: v0.8.0...v0.9.0

Release v0.8.0

⚠️ Notice ⚠️

This release is the last to support Go 1.19. The next release will require at least Go 1.21.

Added

• Add WithPublicEndpoint & WithPublicEndpointFn options. (#43)

Changed

• Upgrade to v1.24.0 of go.opentelemetry.io/otel. (#41)
• Upgrade to v1.20.0 of go.opentelemetry.io/otel/semconv. (#41)
• Adjust Go version for both examples/basic & examples/multi-services to 1.19 & go.opentelemetry.io/otel to v1.24.0. (#41)
• Update otelhttp version to 0.49.0 since it is the version that uses otel 1.24.0 internally, check here for details. (#42)
• Set the go versions in compatibility-test.yml to 1.19, 1.20, & 1.21. (#42)
• Set the sampling strategy to always sample in test cases to avoid random error. (#42)
• Use otlptrace exporter instead of jaeger exporter in examples/multi-services. (#42)

Removed

• Remove the deprecated jaeger exporter from examples/multi-services & use otlptrace exporter instead. (#42)
• Drop support for Go <1.19. (#41)

Full Changelog: v0.7.0...v0.8.0

Release v0.7.0

⚠️ Notice ⚠️

This release is the last to support Go 1.18. The next release will require at least Go 1.19.

Changed

• Upgrade to v1.14.0 of go.opentelemetry.io/otel. (#38)
• Upgrade to v1.17.0 of go.opentelemetry.io/otel/semconv. (#38)
• Adjust Go version for both examples/basic & examples/multi-services to 1.18 & go.opentelemetry.io/otel to v1.14.0. (#38)
• Change http.server_name attributes to net.host.name, this is because semconv is removing this attribute for http. (#38)

Removed

• Remove http.target attribute on implementation & tests based on this comment. (#39)
• Drop support for Go <1.18. (#38)

Full Changelog: v0.6.0...v0.7.0

Release v0.6.0

⚠️ Notice ⚠️

This release is the last to support Go 1.15. The next release will require at least Go 1.18.

Added

• Add WithTraceIDResponseHeader option to enable adding trace id into response header. (#36)
• Add multiple go versions test scripts for local and CI pipeline. (#29)
• Add compatibility testing for ubuntu, macos and windows. (#32)
• Add repo essentials docs. (#33)

Changed

• Upgrade to v5.0.12 of go-chi/chi. (#29)
• Upgrade to v1.10.0 of go.opentelemetry.io/otel. (#29)
• Upgrade to v1.12.0 of go.opentelemetry.io/otel/semconv. (#29)
• Set the required go version for both examples/basic & examples/multi-services to 1.15, go-chi/chi to v5.0.12, & go.opentelemetry.io/otel to v1.10.0 (#35)

New Contributors

• @badygin-yakov made their first contribution in #23
• @ilhamsyahids made their first contribution in #34
• @ProtozoaJr made their first contribution in #36

Full Changelog: v0.5.2...v0.6.0

v0.5.2

What's Changed

• Fixes #26 - Return http.StatusOK (200) as a default http.status_code span attribute by @ajdevries in #30

New Contributors

• @ajdevries made their first contribution in #30

Full Changelog: v0.5.1...v0.5.2

Release v0.5.1

What's Changed

• fix: broken empty routes in chi/v5.0.8 by @xbitres in #18

New Contributors

• @xbitres made their first contribution in #18

Full Changelog: v0.5.0...v0.5.1

Release v0.5.0

What's Changed

• Feat: Add option WithFilter to ignore tracing in certain endpoints as described in #10. Contributed by @hsblhsn.
• Docs: Add multi services example to make it easy for people to get started using otelchi.

Full Changelog: v0.4.0...v0.5.0

Release v0.4.0

What's Changed

• Add Option WithRequestMethodInSpanName() to handle case mentioned in #6.
• Refine description for WithChiRoutes() option to announce it is possible to override the span name in underlying handler with this option.

Full Changelog: v0.3.0...v0.4.0

Release v0.3.0

What's Changed

• Add WithChiRoutes() option to make the middleware able to determine full route pattern on span creation
• Set all known span attributes on span creation rather than set them after request is being executed
• Fix both docker-compose.yml & Dockerfile in example

Full Changelog: v0.2.1...v0.3.0

Release v0.2.1

What's Changed

• Use ctx.RoutePattern() to get span name, this is to strip out noisy wildcard pattern, contributed by @tjefferson08

Full Changelog: v0.2.0...v0.2.1