Harden the 0.2.0 production preview - #2
Merged
Merged
Conversation
Decode captured exports to verify span hierarchy, kinds, and representative attributes. Keep the protobuf decoder test-scoped.
Exercise the LangChain4j OpenAI streaming path with a configured JDK HTTP executor. Verify that the tracing wrapper restores span and request metadata at callback boundaries.
Document the validated OpenAI JDK transport behavior and distinguish callback restoration from provider-internal scheduling. Close the corresponding 0.2 readiness item.
Capture owned-pipeline exporter failures and queue drops through the pinned OpenTelemetry self-metric hooks. Expose bounded no-op reasons and local flush state without inferring application-owned pipeline health.
Register optional health and Micrometer adapters for owned pipeline failures while leaving external OpenTelemetry state explicitly unmanaged.
Describe Actuator status semantics, metric names, external-pipeline limits, and probe guidance for the 0.2 preview.
Run JaCoCo line and branch checks during verify and require coverage artifacts in CI and release validation.
Document the verification command and reports, update release validation notes, and mark the JaCoCo roadmap item complete.
Run SpotBugs and license checks, retain CycloneDX and Trivy evidence, and reject High or Critical dependency vulnerabilities. Align Netty with the first patched 4.1.136.Final release.
Consumer verification only installs already-tested reactor artifacts. Skip JaCoCo there so the install phase does not fail on an intentional zero-test build.
Compare both published modules with 0.1.1 during verify and fail on protected-or-public binary or source incompatibilities. Missing comparison classes remain a hard error.
Move past CVE-2026-45292 and make context fault-injection tests target semantic writes instead of OpenTelemetry SDK-internal write order.
Reject null document and bulk embedding results required to be non-null by Spring AI, while ending the tracing span with an error. Cover both traced and setup-fallback paths.
Document the public core and starter APIs, clarify lifecycle and fail-safe contracts, and fail packaging on Javadoc warnings.
Remove repeated implementation detail and align the migration, support, and release instructions.
Keep Maven version baselines stable while allowing security fixes, and refresh pinned GitHub Actions weekly.
ChoMinGi
marked this pull request as ready for review
July 23, 2026 16:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
This completes the production-readiness pass for the 0.2.0 line.
langfuse-otel-corewithlangfuse-java.Testing
./mvnw -B -ntp clean verify./mvnw -B -ntp -Pquality -DskipTests -Djacoco.skip=true -Dmaven.javadoc.skip=true clean verifyactionlintThe release version change, signed tag, and Central publication remain separate release steps.