Repository navigation
chore(release): fi-instrumentation-otel 1.3.1, traceAI-openai 0.1.14, traceAI-langchain 0.2.2, Java 1.0.3 - #636
Merged
Conversation
…14 and Java 1.0.3 Core 1.3.1 also ships the PII-redaction scoping fixes (#195/#244) that sat under Unreleased, and the 1.3.0 heading gets its release date. OpenAI 0.1.14 also ships the Azure metadata (#154), Baseten (#541), Azure Government (#502), OpenRouter host (#547), full multi-message input (#245) and exhausted-stream changes. Java 1.0.3 also ships #543 and #605. Notes the remaining blank OTEL-env Authorization limitation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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 ships
Version and changelog preparation only; no runtime code or dependency floors change here. Each package ships everything merged since its last release tag, not only the fixes from the last few days. The changelogs now list all of it.
fi-instrumentation-otel1.3.0 → 1.3.1 (sincefi-instrumentation-otel-v1.3.0):Authorizationno longer hides the FI keys, and blank credential headers are skipped.session.id,user.idor conversation ids, and card numbers must be card-shaped and Luhn-valid. Metadata stays redacted.Authorization=inOTEL_EXPORTER_OTLP_HEADERSis still sent with HTTP exporter 1.45+. The released 1.3.0 behaves the same.traceAI-openai0.1.13 → 0.1.14 (sincetraceai-openai-v0.1.13):openrouter.ai;input.value, with the MIME type derived from it;traceAI-langchain0.2.1 → 0.2.2: fix(langchain): restore optional Protect hook on uninstrument #393 restores the optional Protect method on uninstrument.java-v1.0.2; all 28 artifacts move together):generate()with empty default options;TraceConfigrespects theFI_HIDE_*environment flags;Python manifest/runtime versions and release-please entries are synchronized. Every reactor POM and internal parent reference (including example parents) is synchronized; marked Java installation examples track 1.0.3. #413 is an example-only change and needs no package bump. Other package versions and dependency floors remain unchanged.
Read-only live release plan
Captured in a fresh E2B sandbox on 2026-11-10:
NuGet
fi-instrumentation-otel1.0.1 stays unpublished, as on main today; this PR does not change its version or publishing configuration.Java reactor artifacts, all at 1.0.3
Verification
Completed in E2B, not on the local machine:
release_plan.py --check: 155 packages, versions and coverage consistent.release_plan.py --offline: passed.release_plan.py: exactly the three Python versions and Java reactor above, plus the pre-existing NuGet non-delivery. No other unpublished package versions.Reproduce in a disposable remote environment with Python 3.11+ and Node/npm available:
python3 -m unittest discover -s .github/release -p 'test_*.py' python3 .github/release/release_plan.py --check python3 .github/release/release_plan.py --offline python3 .github/release/release_plan.pyThis PR prepares release versions only. Installed-wheel/JAR end-user qualification is tracked by the release coordinator; these planner checks do not claim that coverage. Merging this PR into dev does not publish packages. The maintainer-controlled dev → main release remains separate.
🤖 Generated with Claude Code