Skip to content

Latest commit

 

History

History
109 lines (55 loc) · 3.53 KB

changes.md

File metadata and controls

109 lines (55 loc) · 3.53 KB

2026-10-29 - Run certified Vitest suites on Bun (senpi#4763)

What changed

  • packages/telemetry/package.json: launch the existing temp-owning Vitest runner with bun --bun instead of Node.

Why

  • The full Node and Vitest-on-Bun controls match at 2 files and 15 passing tests. Bun avoids Node test workers.

Why an extension could not handle it

  • Package test scripts select the runtime before extensions load.

Expected merge conflict zones

  • packages/telemetry/package.json: preserve the Bun launcher and forwarded Vitest arguments.

2026-10-10 - Test-run temporary storage has an owner (senpi#3064)

What changed

  • packages/telemetry/package.json: test invocations use scripts/run-tests.mjs so TMPDIR/TEMP/TMP are scoped before the test runtime starts and cleaned after exit.

Why

  • Vitest SSR copies and interrupted fixture writes must not accumulate in the OS temp directory.

Why an extension could not handle it

  • Test-process bootstrap is repository tooling, before runtime extensions load.

Expected merge conflict zones

  • Test command arguments and runtime selection; preserve existing reporters, shards and test filters.

2026-09-30 - Sync with upstream v0.99.1 (6a4af07d6): paths divergent from the new pin

What changed

  • packages/telemetry/src/index.ts: same types as the pinned upstream file; the schema span/event conditional types are laid out the way the fork's formatter prints them.

Why

The fork runs biome with its own formatter over every package (npm run check fails on warnings). No behavior differs from upstream.

Why an extension could not handle it

Source formatting of package files is enforced by the repository check, not by any runtime surface.

Expected merge conflict zones

  • LOW: upstream edits to the TelemetrySchemaSpanEvent* conditional types; take upstream's content and re-format.

2026-09-30 - Sync with upstream v0.99.1 (6a4af07d6): chord, client, protocol, server, telemetry, sqlite-node

What changed

  • packages/telemetry/package.json: resolved by L11 against upstream v0.99.1 (6a4af07d6): upstream constructs adopted, fork behavior kept.

Why

Upstream v0.99.1 (6a4af07d6) changed these paths while the fork carries its own behavior; chord/client/protocol/server/telemetry/sqlite-node take upstream versions with fork exact pins (plan D-12).

Why an extension could not handle it

Package manifests and wire-protocol packages are shared infrastructure below the extension layer.

Expected merge conflict zones

Every path listed above conflicts again where upstream edits the hunks named in its line; the fork-kept constructs named there are the anchors to preserve.

2026-09-29 - Published tarball excludes sourcemaps (senpi#2362)

What changed

  • packages/telemetry/package.json: files excludes dist/**/*.map.

Why

  • The maps point at src/, which is not published, so they cannot resolve for consumers and only add install size.

Why an extension could not handle it

  • Package publish metadata.

Expected merge conflict zones

  • LOW: the files list in package.json.

changes

2026-09-21 - Migrate the test runner to Vitest 5 (senpi#1895)

What changed

  • packages/telemetry/package.json: Updated the test runner to Vitest 5.0.1.

Why

  • Run this workspace on the pinned Vitest 5 release.

Why an extension could not handle it

  • The package manager resolves development tools before extensions load.

Expected merge conflict zones

  • The development dependency pins in packages/telemetry/package.json.