Repository navigation
v0.7.0
Safe defaults: a client can no longer choose trace IDs or learn from responses that an error was logged, and a notifier no longer starts unauthenticated by accident. Breaking: internal services that rely on forwarded request IDs or flush markers must opt in, and StartNotifier needs a signing option; see the migration note below.
Modules released: core v0.7.0, grpcflightrec/v0.4.0, notifier/redisnotifier/v0.4.0 and notifier/natsnotifier/v0.4.0 (each requiring core v0.7.0). otelflightrec is unchanged at v0.3.1.
Changed
-
Safe defaults. Each was an opt-out before; services that only your own services call opt back in:
- Request headers and gRPC metadata (
traceparent,X-Trace-Id,X-Request-Id) no longer choose trace IDs. SetOptions.TrustRequestTraceIDs. - Triggered scopes no longer mark responses with
Flightrec-Flush(gRPC: a trailer). SetOptions.EnableFlushMarker. StartNotifierpanics withoutWithSigningKey. PassWithoutSigning()for a channel that only trusted processes can publish on.
Migration: add
TrustRequestTraceIDs: true, EnableFlushMarker: trueto theOptionsof internal services that use cross-service flush or forward request IDs, and passWithSigningKey(key)(the same key in every service) orWithoutSigning()toStartNotifier. Without the opt-ins, a customGRPCMetadataExtractoris not called, and the notifier and callers match requests only by an OpenTelemetry trace ID, never by a forwardedX-Request-Id. Without a signing option,StartNotifierpanics at startup. Public-facing services that setIgnoreRequestTraceIDsandDisableFlushMarkerneed no change. - Request headers and gRPC metadata (
Added
Options.TrustRequestTraceIDs,Options.EnableFlushMarkerand theWithoutSigningnotifier option.
Deprecated
Options.IgnoreRequestTraceIDsandOptions.DisableFlushMarker: they are the default now. They still override the new options.
Security
- CI runs OpenSSF Scorecard and every fuzz target on each change, and CodeQL scans Go and the workflows.