Skip to content

chore(release): @traceai/fi-core 1.2.1 (process identity privacy fix) - #621

Merged
nik13 merged 3 commits into
mainfrom
dev
Nov 8, 2026
Merged

nik13 merged 3 commits into
mainfrom
dev

Conversation

@nik13

@nik13 nik13 commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Release @traceai/fi-core 1.2.1: a privacy fix.

Why now

Published fi-core 1.2.0 attaches OpenTelemetry's full process detector to every provider's resource. Every span therefore carries:

  • process.command_args, which can hold secrets passed as flags;
  • process.owner, the OS user name;
  • process.executable.path.

A real @traceai/auto@0.1.0 quick-start run today (OpenAI SDK 7, OpenRouter) still exported all three. 1.2.1 keeps only process.runtime.* by default; OTEL_NODE_RESOURCE_DETECTORS opts back in.

Contents (dev → main)

The only manifest change is typescript/packages/fi-core 1.2.0 → 1.2.1. The release workflow publishes that version after its clean-install smoke test.

Testing

🤖 Generated with Claude Code

nik13 and others added 3 commits November 8, 2026 01:51
`pnpm install` on a fresh clone failed: @traceai/copilot and
@traceai/agents build in `prepare`, but @traceai/vscode-extension and the
eight agent packages @traceai/agents imports had no `prepare`, so their
dist/ did not exist yet (TS2307). CI was unaffected because it installs
with --ignore-scripts and builds explicitly.

Give those nine packages the same `prepare: pnpm run build` that the other
39 workspace packages use; pnpm runs prepare in dependency order.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
fi-core 1.2.0 merged OpenTelemetry's full process detector into every
FITracerProvider resource, so process.command_args, process.command,
process.owner, process.executable.path and process.pid went out with
every span. Command-line flags can carry secrets (--api-key=...), and the
OS user name identifies a person.

By default the provider now detects only process.runtime.* (name,
version, description). OTEL_NODE_RESOURCE_DETECTORS, the OpenTelemetry
Node variable, opts in to host, os and process detection (or all/none).
OTEL_SERVICE_NAME and OTEL_RESOURCE_ATTRIBUTES are always applied.

Bumps @traceai/fi-core to 1.2.1.

Fixes #607

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The suite had 4 failing files on dev and nothing ran it on PRs:

- config.test counted every typescript/packages/traceai_* directory as an
  instrumentation; the coding-agent packages (@traceai/agent-core and the
  plugins built on it) are set up with `npx @traceai/agents`, not by the
  zero-code agent. Exclude them by that dependency.
- safety.test passed a Buffer to `new Response()`, which no longer
  type-checks against current @types/node; wrap it in a Uint8Array as the
  same file already does on line 76.
- privacy-catalog S6: fi-core listed src/**/*.json in its tsconfig
  includes, so every consumer's `tsc --build` reference to fi-core
  re-emitted dist/src/privacy.json reserialized, after fi-core's postbuild
  had written the byte-exact copy. tsc no longer emits the catalog; the
  postbuild copies are the only ones (published 1.2.0 bytes were correct).
- round6-boundary B3 needs @traceai/vercel built; it passes once the
  workspace is built in order, as the new workflow does.

Adds .github/workflows/auto-typescript-tests.yml: install, build:ordered,
then the auto suite, on PRs touching auto/fi-core/semconv/spec or any
traceai_* manifest, and on every push to dev.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@nik13 nik13 changed the title release: @traceai/fi-core 1.2.1 (process identity privacy fix) chore(release): @traceai/fi-core 1.2.1 (process identity privacy fix) Nov 8, 2026
@nik13
nik13 merged commit f7f1c1e into main Nov 8, 2026
172 of 192 checks passed
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