chore(repo): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@evlog/cli@0.3.0

Minor Changes

• #459 161260e Thanks @HugoRCD! - feat(cli): add evlog init — an interactive setup that reads the project, then wires evlog into an existing Nuxt, Nitro, Next.js, or TanStack Start app

  It runs the same analysis evlog map runs and offers only what the project can back up: an error catalog when the same createError appears in more than one file, audit actions when sensitive entry points have no trail, the AI SDK and auth integrations when their packages are installed, batching when something actually leaves the process. Offers carry their evidence — "3 repeated errors found" — and the catalogs are seeded with the project's own errors and routes rather than scaffolded from a template

  Development and production destinations are asked for separately, because nobody sends local traffic to Axiom and nobody reads production logs off the box's filesystem. Production takes several destinations at once and fans the event out to each; the generated plugin branches on the environment in one place. Only the filesystem drain is gated to development, and batching wraps the network sends but never the local write

  Config files are patched at the exact AST offsets so comments and formatting survive; existing files are never overwritten, and a drain file that already wires the same destinations is left alone rather than duplicated. Secrets are never prompted for — the adapter's variables are appended to .env.example, never .env. The run finishes by executing evlog doctor, so it answers "did it work" instead of pointing at another command

  Every prompt has a flag, so an agent reproduces exactly what a human just did: --yes, --json, a non-TTY, or CI selects the non-interactive path, and an unknown --drain or --extras value stops the run rather than silently defaulting. Run from a workspace root, it sets up the apps rather than the root package

  init records which options were picked on its telemetry event — framework, destinations, extras, sampling preset, and counts — so the flow can lead with what people use. Every value is an id from the CLI's own catalog behind an allowlist; the service name and anything read out of the user's source are never sent

• #459 44a33b1 Thanks @HugoRCD! - feat(cli): add evlog map --baseline — gates a pull request on regressions against the committed evlog.map.json instead of an absolute threshold, which keeps CI honest across releases that move the rules. Compares per check: a requirement going from pass to fail gates, and so does silencing one with a disable comment. New dark entry points are reported without failing (--min-score is the bar for new work). Reads a local file or git:<ref> — no network, no repository access, so it behaves the same on a private repo. A run that reports a regression leaves the map file untouched rather than ratcheting the baseline down to the worse state

Patch Changes

• #454 2f0e98a Thanks @HugoRCD! - fix(cli): detect Nuxt 4 app/pages (and src/pages) in evlog map — pages under the Nuxt 4 default layout were invisible, which could leave a project at 100/100 with zero entry points

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
evlog-docs	Ready	Preview, Comment, Open in v0	Jul 28, 2026 4:12pm
evlog-telemetry	Ready	Preview, Comment	Jul 28, 2026 4:12pm
just-use-evlog	Ready	Preview, Comment	Jul 28, 2026 4:12pm