All notable changes to this project are documented in this file. The history of the
earlier Python (0.3.0–2.0.0) and JavaScript releases is in the git history: the v2.0.0 tag and main branch for
Python, and the logquill-js repository for JavaScript.
CONTRIBUTING.md covering repository layout, per-language setup, the contract and versioning rules, testing and quality expectations, review and merge, CI, dependencies, security reporting, releases and licensing of contributions.docs/ (architecture, the cross-language contract, versioning and stability, releasing, supply chain, API names, migration guides), a support policy, and a refreshed README for the repository and every language binding. The maintainer-only planning notes are no longer part of the repository.pip install logquill now installs the logquill command (tail, trace, dev, serve, verify) and python -m logquill.cli works, as in 2.0.0. The 3.0.0rc8 wheel had neither: its pyproject.toml declared no script and the logquill.cli module was gone. The command is the logquill-cli Rust program compiled into the extension module (logquill_cli::cli::run), so the standalone binary and the Python script behave the same and no extra install or per-platform binary is needed.@logquill/wasm and the macOS native packages only).python-vX.Y.Z (or crates-, npm-, ruby-, nuget-, maven-, go-, swift-) runs only that language’s tests and publish jobs; vX.Y.Z still releases everything. A failing or unconfigured registry no longer blocks the others, and the Python timing benchmark only warns on a release tag.core.wasm was still rc.1, and the other registries still needed their trusted publishers, tokens and secrets. CI now checks that the committed core.wasm matches the workspace version, so a stale one fails on the pull request.@logquill/wasm and the macOS native packages), so those versions could not be published again by the release workflow. The Maven group ID is now io.github.nikhilvdev, because the logquill.io domain behind io.logquill is not ours; the Java package stays io.logquill.develop branch is now the 3.0 line. The Python library source was removed
from it and replaced by a small Rust workspace (logquill-core, logquill-cli), the
shared record schema and fixtures (schema/), and the plan, behaviour specification,
publishing guide and API-name table (docs/). The 2.x Python releases remain on main
and under the v2.0.0 tag.schema/corpus/ — 22 groups and 865 cases, generated by running
the Python 2.0.0 release and the JavaScript source on one set of hostile inputs and
applying the settled decisions — with the generator in scripts/corpus/, a scheduled check
that the references still produce it, and a report of every place the two releases
disagreed (docs/spec/10-corpus-divergences.md). Decisions D35–D45 record what was settled.logquill-core reads and builds records, levels, timestamps and the llm block;
writes Python-compatible canonical JSON; hash-chains, signs and verifies logs; applies the
content-capture policy; and has the retry tracker and per-logger enable/disable rules. It
passes the shared golden records, the golden chain and the corpus groups that cover them.logquill verify FILE [--sign-key HEX --signature HEX] checks a hash-chained JSONL log
and prints the same results as the Python command.logquill-core — trace-header and id parsing, key and PII
redaction, JSON / text / logfmt lines, GenAI attributes and ECS documents, SQL and graph rows,
the trace-tree builder, the sampling, rate-limit, adaptive-sampling, flight-recorder,
run-summary and alert-dedupe state machines, and the log-call pipeline, which withholds a
record when a redactor fails. All of it passes the shared corpus.logquill-runtime, the threads, files and sockets around the core: a bounded queue and one worker thread with
drop_oldest, drop_newest and block, restart after fork, the console and rotating file transports (size rotation,
gz / zip compression, Fernet encryption), batched HTTP, Datadog, New Relic, Elasticsearch and Application Insights
sinks, syslog, SQLite, OTLP traces and logs, Slack / PagerDuty / email alerting, StatsD / pushgateway / OTLP metrics, and
level file and environment watchers.logquill command with tail, trace, dev, serve and verify, and the embedded local trace viewer.bindings/python), a compiled abi3 wheel on the Rust core. It keeps the 2.0.0 Python API and
differs from 2.0.0 only where a decision says so; see docs/migrating/python-2-to-3.md. Per-call latency is lower than 2.0.0.bindings/node), a napi-rs addon with a WebAssembly fallback, at parity with the
Python package; see docs/migrating/js-1-to-3.md. Node 22 or later.bindings/wasm): the core as a WebAssembly module (320 KB gzipped), with the SDK built for
browsers. The shared corpus passes in Node, Deno, Bun, headless Chrome and Cloudflare Workers.crates/logquill-ffi, header include/logquill.h) and bindings built on it for Ruby (ffi gem), .NET
(P/Invoke), Go (WebAssembly through wazero, no cgo), Swift (an XCFramework) and the JVM (JNA). Each has a README example that
is run by its tests. The logger config accepts the redact, pii, sampling, rate_limit and adaptive_sampling plugins.parse_lenient in logquill-core, the reader that accepts NaN and Infinity.regex dependency no longer enables its default features; the regex-perf feature (on by default) and
regex-perf-web choose how much speed to trade for module size.RedactPlugin matches keys at every depth, and JSON lines are UTF-8. The full list is in
docs/migrating/python-2-to-3.md.LogfmtFormatter in the Node SDK threw a RangeError when meta held an invalid Date; it now writes Invalid Date.Plugins / PluginConfig builders for sampling, rate_limit and adaptive_sampling in the Ruby, .NET, Go, Swift and
JVM bindings; NewRotatingFileTransport in Go; scripts/check-versions.py; and migration guides for Python 2.x and JS 1.x.LICENSE, and a licence field in every package); Python 2.0.0 stays FSL-1.1-MIT as published.
All manifests are at 3.0.0-rc.1 and scripts/check-versions.py keeps them in step..github/workflows/release.yml, which on a version tag checks the manifests, runs the full CI, and publishes to crates.io,
PyPI and npm (@logquill/wasm, and logquill with its @logquill/native-* platform packages), RubyGems, NuGet and Maven Central
(a signed bundle, held in the portal for a manual release), tags the Go module, and publishes the Swift mirror. Nothing has been
released with it yet.core.wasm and exposes CoreVersion(); NewRotatingFileTransport is new.