Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
chore/workspace-caret-internal-deps
91955524 test(ai): expect the preserved UI message id in the createdAt round-trip `should preserve createdAt for assistant segments and tool results` asserted an exact `toEqual` on the model messages without an `id`, so it broke on `main` once #1066 started stamping `uiMessage.id` onto every model message a UI message fans out into. The two changes landed independently: #1066 merged first, but #1069's branch predated it and was not re-tested before merge, so the conflict only appeared after both were on `main`. Fix the expectation rather than the converter. Propagating the id is the intended behaviour from #1066 -- a single UI message can fan out into several model messages and persistence needs the shared identity -- so dropping it would revert that feature and break its own tests.
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
91955524 Merge 6cd8ff4ff9723e12ed1c6bec12c35a3a6224f16d into fdb791a1c9c8de906eecf76f59743f697621b027
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
91955524 Merge 6cd8ff4ff9723e12ed1c6bec12c35a3a6224f16d into fdb791a1c9c8de906eecf76f59743f697621b027
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
66769381 fix: publish internal dependency ranges as ^x.y.z instead of exact pins Internal dependencies on other TanStack AI packages used `workspace:*` in `dependencies` and `peerDependencies`. pnpm rewrites `workspace:*` to an exact version at publish time, so released packages asked for `@tanstack/ai-utils@0.4.0` rather than `^0.4.0`. An exact pin cannot dedupe, so consumers installing a newer `@tanstack/ai` alongside a package pinned to the previous patch ended up with two copies of the library. An exactly pinned peerDependency is worse: it conflicts as soon as the internal package ships its next patch. `@tanstack/ai-isolate-daytona` and `@tanstack/ai-isolate-quickjs-bun` shipped with `"@tanstack/ai-code-mode": "0.3.10"` as an exact peer dep and would have broken on `ai-code-mode@0.3.11`. Switch the published-facing fields (`dependencies`, `peerDependencies`, `optionalDependencies`) to `workspace:^` across 35 packages. Every package here is still 0.x, so `^0.43.1` resolves to `0.43.x` only: patches dedupe cleanly and no breaking minor is pulled in. This also removes an existing inconsistency, as peerDependencies were already 43 x `workspace:^` against 10 x `workspace:*`. `devDependencies` keep `workspace:*` because they are never published and `*` correctly means "always build against the local copy". Private packages (`examples/`, `testing/`) keep `workspace:*` for the same reason. Document the split in CLAUDE.md, which previously advised `workspace:*` everywhere. Also resync pnpm-lock.yaml with packages/ai-angular/package.json. #1068 bumped the Angular manifest but left the lockfile at `^21.2.0`, so `pnpm install --frozen-lockfile` was failing on main.
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
66769381 fix: publish internal dependency ranges as ^x.y.z instead of exact pins Internal dependencies on other TanStack AI packages used `workspace:*` in `dependencies` and `peerDependencies`. pnpm rewrites `workspace:*` to an exact version at publish time, so released packages asked for `@tanstack/ai-utils@0.4.0` rather than `^0.4.0`. An exact pin cannot dedupe, so consumers installing a newer `@tanstack/ai` alongside a package pinned to the previous patch ended up with two copies of the library. An exactly pinned peerDependency is worse: it conflicts as soon as the internal package ships its next patch. `@tanstack/ai-isolate-daytona` and `@tanstack/ai-isolate-quickjs-bun` shipped with `"@tanstack/ai-code-mode": "0.3.10"` as an exact peer dep and would have broken on `ai-code-mode@0.3.11`. Switch the published-facing fields (`dependencies`, `peerDependencies`, `optionalDependencies`) to `workspace:^` across 35 packages. Every package here is still 0.x, so `^0.43.1` resolves to `0.43.x` only: patches dedupe cleanly and no breaking minor is pulled in. This also removes an existing inconsistency, as peerDependencies were already 43 x `workspace:^` against 10 x `workspace:*`. `devDependencies` keep `workspace:*` because they are never published and `*` correctly means "always build against the local copy". Private packages (`examples/`, `testing/`) keep `workspace:*` for the same reason. Document the split in CLAUDE.md, which previously advised `workspace:*` everywhere. Also resync pnpm-lock.yaml with packages/ai-angular/package.json. #1068 bumped the Angular manifest but left the lockfile at `^21.2.0`, so `pnpm install --frozen-lockfile` was failing on main.
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
66769381 Merge f328b82d8e03f7a04541d7b61d4a1f5846b28df8 into fdb791a1c9c8de906eecf76f59743f697621b027
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
ff327f7c fix: publish internal dependency ranges as ^x.y.z instead of exact pins Internal dependencies on other TanStack AI packages used `workspace:*` in `dependencies` and `peerDependencies`. pnpm rewrites `workspace:*` to an exact version at publish time, so released packages asked for `@tanstack/ai-utils@0.4.0` rather than `^0.4.0`. An exact pin cannot dedupe, so consumers installing a newer `@tanstack/ai` alongside a package pinned to the previous patch ended up with two copies of the library. An exactly pinned peerDependency is worse: it conflicts as soon as the internal package ships its next patch. `@tanstack/ai-isolate-daytona` and `@tanstack/ai-isolate-quickjs-bun` shipped with `"@tanstack/ai-code-mode": "0.3.10"` as an exact peer dep and would have broken on `ai-code-mode@0.3.11`. Switch the published-facing fields (`dependencies`, `peerDependencies`, `optionalDependencies`) to `workspace:^` across 35 packages. Every package here is still 0.x, so `^0.43.1` resolves to `0.43.x` only: patches dedupe cleanly and no breaking minor is pulled in. This also removes an existing inconsistency, as peerDependencies were already 43 x `workspace:^` against 10 x `workspace:*`. `devDependencies` keep `workspace:*` because they are never published and `*` correctly means "always build against the local copy". Private packages (`examples/`, `testing/`) keep `workspace:*` for the same reason. Document the split in CLAUDE.md, which previously advised `workspace:*` everywhere. Also resync pnpm-lock.yaml with packages/ai-angular/package.json. #1068 bumped the Angular manifest but left the lockfile at `^21.2.0`, so `pnpm install --frozen-lockfile` was failing on main.
by Alem Tuzlak
Failed
chore/workspace-caret-internal-deps
ff327f7c Merge 2538d962a58f75ef2c106676f3c8631edcf5cc01 into fdb791a1c9c8de906eecf76f59743f697621b027
by Alem Tuzlak
Succeeded
chore/workspace-caret-internal-deps
ff327f7c Merge 2538d962a58f75ef2c106676f3c8631edcf5cc01 into fdb791a1c9c8de906eecf76f59743f697621b027
by Alem Tuzlak