Skip to content

chore(release): merge dev into main (traceAI 2026-11-18: sampler parity, sampling ratio, Mastra, Node orphan fix) - #718

Merged
nik13 merged 99 commits into
mainfrom
release/main-1118
Nov 18, 2026
Merged

nik13 merged 99 commits into
mainfrom
release/main-1118

Conversation

@nik13

@nik13 nik13 commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Merges dev into main to release the traceAI changes merged since #708.

The merge commit brings main's earlier release merges into dev's history; its tree is identical to dev (99f1d99).

What publishes when this merges

  • PyPI: fi-instrumentation-otel 1.5.0 (OTEL_TRACES_SAMPLER honoured when FI_SAMPLE_RATE is unset, fi.sampling.ratio, FI_TRACES_URL), traceAI-temporal 0.1.1 (FI_TRACES_URL)
  • npm: @traceai/auto 0.3.0 (OTEL_TRACES_SAMPLER, fi.sampling.ratio, no orphan trace under a dropped incoming request), @traceai/fi-core 1.4.0 (FI_TRACES_URL, ratio kept on export), @traceai/mastra 0.2.3 (GenAI format from the installed converter)
  • Maven Central: Java SDK 1.3.0, including traceai-javaagent (sampler option, fi.sampling.ratio)
  • Go: tag go/auto/v0.2.0

Included PRs: #709, #710, #711, #713, #714, #715, #717.

Not in this release

Verification

nik13 and others added 30 commits November 17, 2026 03:14
… trusted publishing for traceai-auto and traceai-roast
…usted publishing; point go/auto docs at v0.1.0
Self-hosted Docker installs serve the platform API and the trace collector on different ports, but exports and API calls both read FI_BASE_URL, so one shell could not reach both. FI_TRACES_URL now names the trace destination for HTTP exports in Python (register, HTTPSpanExporter, the default exporter, Endpoints, the Temporal helper) and TypeScript fi-core. Unset or blank keeps FI_BASE_URL; custom eval API calls always use FI_BASE_URL.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…TEL_TRACES_SAMPLER when FI_SAMPLE_RATE is not set
…t honours OTEL_TRACES_SAMPLER when FI_SAMPLE_RATE is not set
feat: honour OTEL_TRACES_SAMPLER and add sampler options across the traceAI SDKs
nik13 and others added 26 commits November 17, 2026 14:52
feat: fi.sampling.ratio on spans kept by head sampling across the traceAI SDKs
The published-core compatibility checks import this otel.py next to a
released fi_instrumentation package whose settings has no
get_env_traces_endpoint. Fall back to the same rule locally there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(mastra): select the GenAI format for the installed converter
Cover awaited nested-call and explicit parents with and without a previous span. Before the fix, both keep the ended request. The existing cross-language cases also fail in the ordinary Node-only environment because they launch system Python.
Track dropped request lifetimes weakly across package copies. When a helper or explicit parent carries an ended request, restore the previous parent span without replacing its derived context values.
feat(fi-core): send span exports to FI_TRACES_URL when set
chore(release): publish NuGet and RubyGems packages through gated trusted publishing
fix(auto): honour a dropped incoming parent in the zero-code Node agent
…poral 0.1.1

fi-instrumentation-otel 1.4.0 was released from main 3c00a1d, so the
changes merged to dev since then go out as 1.5.0: FI_TRACES_URL (#710),
OTEL_TRACES_SAMPLER/_ARG on agent-owned providers (#711) and the
fi.sampling.ratio attribute with fi=r:<ratio> tracestate (#713). The
changelog moves the FI_TRACES_URL and sampler lines out of the published
1.4.0 section, dates 1.4.0, and adds the sampling-ratio line.

traceAI-temporal's configure() now sends span exports to FI_TRACES_URL
when it is set (#710), so the package goes out as 0.1.1 with its README
install pin.
…nd @traceai/mastra 0.2.3

@traceai/fi-core 1.3.0, @traceai/auto 0.2.0 and @traceai/mastra 0.2.2 were
released from main 3c00a1d, so the changes merged to dev since then go out
as new versions.

- fi-core 1.4.0: FI_TRACES_URL (#710) and keeping a valid fi.sampling.ratio
  on exports under attribute limits (#713). The FI_TRACES_URL line moves out
  of the published 1.3.0 section.
- auto 0.3.0: the agent's own provider follows OTEL_TRACES_SAMPLER/_ARG when
  no rate is set (#711), which drops AI spans under unsampled parents, so it
  gets a minor version with an upgrade note; fi.sampling.ratio and
  fi=r:<ratio> tracestate (#713); a dropped incoming parent no longer leaves
  an orphan trace (#715). The sampler line moves out of the published 0.2.0
  section, and the 0.2.0 FI_SAMPLE_RATE upgrade line is restored to its
  released wording. auto keeps its workspace:* fi-core dependency, which
  publishes as exactly 1.4.0.
- mastra 0.2.3: the GenAI format follows the installed
  @mastra/otel-exporter version (#714).
go/auto/v0.1.0 was tagged from main 3c00a1d. Since then go/auto gained
OTEL_TRACES_SAMPLER/_ARG on agent-owned providers (#711) and the
fi.sampling.ratio attribute with fi=r:<ratio> tracestate (#713), so it is
released as go/auto/v0.2.0. The changelog moves the sampler line out of the
Unreleased section, which says no Go release is published, into a go/auto
0.2.0 section. No other Go module changed since 3c00a1d.
Java SDK 1.2.0 was released from main 3c00a1d. Since then the reactor
gained OTEL_TRACES_SAMPLER/_ARG on core-owned and agent providers with
TraceConfig.Builder.sampler(Sampler) (#711), and the fi.sampling.ratio
attribute with fi=r:<ratio> tracestate (#713), so every module goes out
as 1.3.0. The parent and every module, example and BOM parent reference,
the compatibility consumer's traceai.version, the README install snippets
and the javaagent download example move to 1.3.0. The changelog moves the
sampler line out of the old Unreleased section into 1.3.0, adds the
sampling-ratio line, and dates 1.2.0.
chore(release): version Python 1.5.0, npm auto 0.3.0 / fi-core 1.4.0 / mastra 0.2.3, go/auto 0.2.0, Java 1.3.0
@nik13
nik13 merged commit 2eb1722 into main Nov 18, 2026
355 checks passed
@nik13
nik13 deleted the release/main-1118 branch November 18, 2026 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant