diff --git a/.changeset/evlog-bin-no-refetch-loop.md b/.changeset/evlog-bin-no-refetch-loop.md deleted file mode 100644 index a5f29ba5..00000000 --- a/.changeset/evlog-bin-no-refetch-loop.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"evlog": patch ---- - -`pnpm dlx evlog ` and `pnpm dlx @evlog/cli ` work on pnpm 11 instead of hanging. pnpm 11 links packages from its global store, so the `evlog` bin in a dlx install could not find the `@evlog/cli` installed next to it and fetched it again, forever. The bin now also looks for `@evlog/cli` from the `node_modules/.bin` folder that launched it. If a fetch it started still lands back on it, it exits with status 1 and suggests `npx --yes @evlog/cli ` instead of fetching a third time. diff --git a/.changeset/init-config-typechecks-before-prepare.md b/.changeset/init-config-typechecks-before-prepare.md deleted file mode 100644 index 600e82ea..00000000 --- a/.changeset/init-config-typechecks-before-prepare.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@evlog/cli": patch ---- - -`evlog init` now writes `evlog.config.ts` with `process.env.NODE_ENV` in place of `import.meta.dev` for Nuxt, Nitro and TanStack Start, the same condition Next, Hono, Express and Fastify already used. The generated file no longer reports `Property 'dev' does not exist on type 'ImportMeta'` in a fresh Nuxt project before `nuxi prepare` has run. The production drain is still selected in a Nuxt production build, because Nitro inlines `NODE_ENV` there. Existing `evlog.config.ts` files are not rewritten; change the condition by hand to pick this up. diff --git a/.changeset/logs-error-status-field.md b/.changeset/logs-error-status-field.md deleted file mode 100644 index f8581fea..00000000 --- a/.changeset/logs-error-status-field.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@evlog/cli": patch ---- - -`evlog logs` and the NuxtHub log viewer now show the HTTP status of an error from `error.status`, falling back to `error.statusCode` for files written before v3. Before, a v3 error event rendered no status, and a 2.x error created with only `status` (for example a plain h3 error) rendered none either. diff --git a/.changeset/nitro-drain-hook-undefined.md b/.changeset/nitro-drain-hook-undefined.md deleted file mode 100644 index f5d6caa3..00000000 --- a/.changeset/nitro-drain-hook-undefined.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"evlog": patch ---- - -The Nitro plugin and the client ingest route no longer throw `Cannot read properties of undefined (reading 'catch')` on every request under Nitro 3. hookable 6 returns `undefined` from `callHook` when no `evlog:drain` hook is registered or every registered hook is synchronous, and evlog now accepts that. diff --git a/.changeset/signals-evaluation-question-kinds.md b/.changeset/signals-evaluation-question-kinds.md deleted file mode 100644 index ecdd65ad..00000000 --- a/.changeset/signals-evaluation-question-kinds.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@evlog/signals": patch ---- - -`EvaluationQuestion` and `EvaluationAnswer` cover only the `boolean`, `choice` and `score` types a signal asks. Recent `ai` 7 releases added a `box` question type, which made an exhaustive `switch` over `question.type` in a custom `AnswerFn` fail to type-check. diff --git a/.changeset/vite-reads-evlog-config.md b/.changeset/vite-reads-evlog-config.md deleted file mode 100644 index cf74f270..00000000 --- a/.changeset/vite-reads-evlog-config.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"evlog": minor ---- - -The `evlog/vite` plugin now reads `evlog.config.ts` from the Vite root, the same file the CLI, Nuxt and Nitro read, so Vite-based apps (TanStack Start, React Router, SvelteKit, Astro) can keep their settings in the shared file. The file is the base and plugin options override it key by key. Only the serializable settings (`service`, `environment`, `enabled`, `pretty`, `silent`, `sampling`, `minLevel`, `stringify`) are read from the file; its functions (`drain`, `enrich`, `keep`, `plugins`) are not injected by the plugin. Without a file, the plugin output is unchanged. A file that fails to load fails the build with its path in the error. diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index 2f6bb07b..12c9cb71 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,13 @@ # @evlog/cli +## 0.11.1 + +### Patch Changes + +- [#945](https://github.com/evloghq/evlog/pull/945) [`17b0411`](https://github.com/evloghq/evlog/commit/17b04119f4a162f5103512eaa90dc03dfb1cc117) Thanks [@evlogai](https://github.com/apps/evlogai)! - `evlog init` now writes `evlog.config.ts` with `process.env.NODE_ENV` in place of `import.meta.dev` for Nuxt, Nitro and TanStack Start, the same condition Next, Hono, Express and Fastify already used. The generated file no longer reports `Property 'dev' does not exist on type 'ImportMeta'` in a fresh Nuxt project before `nuxi prepare` has run. The production drain is still selected in a Nuxt production build, because Nitro inlines `NODE_ENV` there. Existing `evlog.config.ts` files are not rewritten; change the condition by hand to pick this up. + +- [#949](https://github.com/evloghq/evlog/pull/949) [`20aaa2c`](https://github.com/evloghq/evlog/commit/20aaa2c271721e195c13d083ee0ee92d030bd9a2) Thanks [@evlogai](https://github.com/apps/evlogai)! - `evlog logs` and the NuxtHub log viewer now show the HTTP status of an error from `error.status`, falling back to `error.statusCode` for files written before v3. Before, a v3 error event rendered no status, and a 2.x error created with only `status` (for example a plain h3 error) rendered none either. + ## 0.11.0 ### Minor Changes diff --git a/packages/cli/package.json b/packages/cli/package.json index 7cbde6cd..e2b51618 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@evlog/cli", - "version": "0.11.0", + "version": "0.11.1", "description": "The official command line for evlog", "author": "HugoRCD ", "homepage": "https://evlog.dev", diff --git a/packages/evlog/CHANGELOG.md b/packages/evlog/CHANGELOG.md index 4ba12d44..b6f6c038 100644 --- a/packages/evlog/CHANGELOG.md +++ b/packages/evlog/CHANGELOG.md @@ -1,5 +1,17 @@ # evlog +## 2.34.0 + +### Minor Changes + +- [#918](https://github.com/evloghq/evlog/pull/918) [`e3b6ab2`](https://github.com/evloghq/evlog/commit/e3b6ab259a44c7b037056b19e4c41ced153731fa) Thanks [@evlogai](https://github.com/apps/evlogai)! - The `evlog/vite` plugin now reads `evlog.config.ts` from the Vite root, the same file the CLI, Nuxt and Nitro read, so Vite-based apps (TanStack Start, React Router, SvelteKit, Astro) can keep their settings in the shared file. The file is the base and plugin options override it key by key. Only the serializable settings (`service`, `environment`, `enabled`, `pretty`, `silent`, `sampling`, `minLevel`, `stringify`) are read from the file; its functions (`drain`, `enrich`, `keep`, `plugins`) are not injected by the plugin. Without a file, the plugin output is unchanged. A file that fails to load fails the build with its path in the error. + +### Patch Changes + +- [#946](https://github.com/evloghq/evlog/pull/946) [`c7c5d8c`](https://github.com/evloghq/evlog/commit/c7c5d8c2d611ec1dfdf99998d650db2df1eb6892) Thanks [@evlogai](https://github.com/apps/evlogai)! - `pnpm dlx evlog ` and `pnpm dlx @evlog/cli ` work on pnpm 11 instead of hanging. pnpm 11 links packages from its global store, so the `evlog` bin in a dlx install could not find the `@evlog/cli` installed next to it and fetched it again, forever. The bin now also looks for `@evlog/cli` from the `node_modules/.bin` folder that launched it. If a fetch it started still lands back on it, it exits with status 1 and suggests `npx --yes @evlog/cli ` instead of fetching a third time. + +- [#927](https://github.com/evloghq/evlog/pull/927) [`b395334`](https://github.com/evloghq/evlog/commit/b395334d68b5737a0c08b7d4477194c4f140af86) Thanks [@nathanchase](https://github.com/nathanchase)! - The Nitro plugin and the client ingest route no longer throw `Cannot read properties of undefined (reading 'catch')` on every request under Nitro 3. hookable 6 returns `undefined` from `callHook` when no `evlog:drain` hook is registered or every registered hook is synchronous, and evlog now accepts that. + ## 2.33.1 ### Patch Changes diff --git a/packages/evlog/package.json b/packages/evlog/package.json index 0e581203..2215acde 100644 --- a/packages/evlog/package.json +++ b/packages/evlog/package.json @@ -1,6 +1,6 @@ { "name": "evlog", - "version": "2.33.1", + "version": "2.34.0", "description": "Modern TypeScript logger — simple logs, wide events, structured errors. Built for scripts, libraries, jobs, edge, and HTTP. One drain pipeline everywhere.", "author": "HugoRCD ", "homepage": "https://evlog.dev", diff --git a/packages/signals/CHANGELOG.md b/packages/signals/CHANGELOG.md index 83b01681..2e08fa62 100644 --- a/packages/signals/CHANGELOG.md +++ b/packages/signals/CHANGELOG.md @@ -1,5 +1,11 @@ # @evlog/signals +## 0.2.2 + +### Patch Changes + +- [#955](https://github.com/evloghq/evlog/pull/955) [`d96a2ad`](https://github.com/evloghq/evlog/commit/d96a2adaca00b241b55ebeaa1218e77aca0eb3ec) Thanks [@renovate](https://github.com/apps/renovate)! - `EvaluationQuestion` and `EvaluationAnswer` cover only the `boolean`, `choice` and `score` types a signal asks. Recent `ai` 7 releases added a `box` question type, which made an exhaustive `switch` over `question.type` in a custom `AnswerFn` fail to type-check. + ## 0.2.1 ### Patch Changes diff --git a/packages/signals/package.json b/packages/signals/package.json index e6693eaa..e4d4b011 100644 --- a/packages/signals/package.json +++ b/packages/signals/package.json @@ -1,6 +1,6 @@ { "name": "@evlog/signals", - "version": "0.2.1", + "version": "0.2.2", "description": "Typed model judgments on evlog wide events, built on the AI SDK evaluate contract", "author": "HugoRCD ", "homepage": "https://evlog.dev",