Skip to content

SledTrace v0.6.0 — Local CLI / Startup UX

Choose a tag to compare

View all tags
@Schromeo Schromeo released this 09 Sep 01:45
· 10 commits to main since this release
v0.6.0
392edd1

SledTrace v0.6.0 — Local CLI / Startup UX

Summary

SledTrace v0.6.0 adds a small package-installed CLI and makes its serving boundary explicit. The CLI works after editable or wheel installation, while local service startup remains source-checkout based.

This release does not turn the Python wheel into a standalone SledTrace runtime.

CLI behavior

Available commands:

sledtrace --help
sledtrace serve --help
sledtrace version
sledtrace serve
  • sledtrace --help describes the installed CLI.
  • sledtrace serve --help explains that serving requires a source checkout.
  • sledtrace version prints 0.6.0.
  • sledtrace serve walks upward from the current working directory to locate a SledTrace checkout.
  • Inside a checkout, serve delegates to scripts/start-sledtrace.py.
  • Outside a checkout, serve exits non-zero and explains how to run from the repository or use Docker Compose.

The checkout markers are:

  • AGENTS.md
  • docker-compose.yml
  • scripts/start-sledtrace.py

Standalone wheel limitation

The v0.6.0 wheel does not bundle:

  • the Go Collector binary
  • the Dashboard production build or Node runtime
  • Docker images or Compose runtime assets
  • platform-specific startup binaries

As a result, normal wheel installation supports CLI help and version reporting, but not standalone serving. Run sledtrace serve from inside a SledTrace source checkout, or use docker compose up --build from the repository root.

Compatibility guarantees

  • preferred import remains sledtrace
  • temporary raglens import compatibility remains available
  • preferred collector variable remains SLEDTRACE_COLLECTOR_URL
  • legacy RAGLENS_COLLECTOR_URL fallback remains available
  • the existing repo-local startup script remains the serve backend
  • collector API routes and payload contracts are unchanged
  • SQLite schema and legacy database compatibility are unchanged
  • Dashboard data contract is unchanged

Validation

Validated on 2026-09-07:

cd sdk/python
pytest -q
python -m build
python scripts/validate-wheel.py

cd collector/go
go test ./... -count=1

cd dashboard/web
npm.cmd run build

Observed results:

  • Python SDK: 17 tests passed; output included the expected legacy raglens deprecation warning and an environment-specific .pytest_cache permission warning
  • packaging: sledtrace-0.6.0.tar.gz and sledtrace-0.6.0-py3-none-any.whl built successfully
  • clean wheel environment: import sledtrace, from sledtrace import trace, and import raglens passed
  • clean wheel CLI: root help, serve --help, and version passed
  • clean wheel serve: returned the expected non-zero status and documented source-checkout guidance outside a checkout
  • editable installation: succeeded
  • repo detection: located the checkout from a nested repository directory
  • repo-local delegation: passed under a subprocess test double, without starting long-running services
  • Go Collector: all packages and tests passed
  • Dashboard: TypeScript and Vite production build passed

Unchanged product scope

v0.6.0 introduces no new product functionality beyond CLI/startup UX:

  • supported span types remain retrieval and llm
  • existing deterministic warning rules are unchanged
  • no new warning rules or LLM-as-judge behavior
  • no collector protocol changes
  • no storage schema changes
  • no Dashboard data-contract changes
  • no LangChain or LlamaIndex adapters
  • no cloud, authentication, hosted Collector, or PyPI publication

Release state

Released on 2026-09-08.

The release commit also removed tracked Python bytecode/cache artifacts and added repository ignore coverage so routine Python test runs do not pollute the working tree.

Assets 2
Loading