⬆️ chore: upgrade actions/checkout to v7 across all workflows
- Bump actions/checkout from v3/v4/v6 to v7 (latest release v7.0.1) in 36 files (61 references)
- Includes workflows, docs example, keeping version references consistent
- Note: v7 blocks checking out fork PRs for pull_request_target / workflow_run triggers by default (safer defaults); verified existing usages only checkout the base ref so no behavior change expected
Co-authored-by: Arvin Xu <arvinxx@users.noreply.github.com>
* 👷 build: upgrade vitest to 5.0.0
Bump vitest and @vitest/coverage-v8 to 5.0.0 and migrate the configs for Vitest 4/5: drop the removed coverage.all option and replace poolOptions.forks.singleFork with maxWorkers/isolate.
* 👷 build: shim jest-dom matcher types for vitest 5
Vitest 5 exposes Assertion<R, T> and no longer reads the jest.Matchers augmentation that @testing-library/jest-dom ships, so its matchers vanish from expect(). Re-declare them on the Vitest interface, and replace the removed describe.sequential with { concurrent: false }.
* 👷 build: migrate the test suite to vitest 5
Vitest 5 (and @vitest/coverage-v8) replaces the esbuild dep optimizer with Rolldown, removed environmentMatchGlobs/coverage.all/poolOptions, forwards `new` to mock implementations, requires top-level vi.mock, and no longer resets automocks in restoreAllMocks. Migrate the root config to app/server projects with Rolldown optimizer options, shim the jest-dom matchers on Assertion<R, T>, and update the affected tests (constructor mocks, hoisted mocks, awaited assertions, explicit mock types, per-test mock defaults).
* 👷 build: make the openapi knowledge-base FileService mock constructable
tests/ was outside the per-area sweep; vitest 5 forwards `new` to the mock implementation, so the arrow implementation threw "is not a constructor".
* 👷 build: point the CI blob-report artifacts at the vitest 5 output dir
Vitest 5 writes blob reports to .vitest/blob instead of .vitest-reports, so the sharded jobs uploaded nothing and the merge jobs failed with ENOENT. Track the new directory in .gitignore too.
* 👷 build: refresh the desktop lockfile for vitest 5
apps/desktop/pnpm-lock.yaml is committed and the desktop build action installs with --frozen-lockfile, so the vitest/override change has to be reflected in it.
* 👷 build: keep the pre-vitest-4 coverage exclusions explicit
Vitest 4+ ships an empty coverageConfigDefaults.exclude, so configs that spread it silently lost the default exclusions (node_modules, dist, *.config.*) and counted more files. Inline the previous list.
* 🎨 style: format the migrated vitest configs
* 👷 build: keep canary's new class mocks constructable under vitest 5
exploreGraph/dispatchAuthorization/scopedDevices (canary #19375, #19352) mock classes with arrow implementations; vitest 5 constructs the implementation when the mock is newed, so the arrows throw 'is not a constructor'.
* 👷 build: migrate workspace to pnpm 12
pnpm 12 no longer reads the package.json "pnpm" field, only honours auth and registry keys from .npmrc, and requires allowBuilds instead of onlyBuiltDependencies. Move every project setting into pnpm-workspace.yaml and keep the previously effective overrides and build allowlist.
* 👷 build: resolve desktop and cli workspaces on pnpm 12
pnpm 12 no longer accepts './'-prefixed workspace package globs, so the desktop stub path is now relative without the prefix. Migrate the remaining package.json "pnpm" fields into the desktop and cli pnpm-workspace.yaml files.
* 👷 build: list protobufjs in the desktop build allowlist
pnpm 12 fails the install with ERR_PNPM_IGNORED_BUILDS when a script-bearing dependency is missing from allowBuilds. protobufjs only appears in the desktop graph on Linux, so it was absent from the previous allowlist.
* 👷 build: relink root workspace members before the desktop typecheck
pnpm 12 writes broken relative symlinks for workspace members that live outside the desktop workspace root (../../packages/*), so tsgo cannot resolve sibling packages from source. Installing the root workspace after the desktop install rewrites those links correctly.
* ✨ feat(chat-input): nudge sandbox users to switch to local
When a desktop user has the cloud sandbox selected as the execution
target, show an inline notice above the input with a one-click "switch
to local" action. Sandbox is ephemeral, so local runs are faster and
can access the user's files.
- Rename CurrentModelNotice -> ChatInputNotice; the resolver now returns
{ key, type, action } so it can carry both warning (model) and info
(sandbox) notices in a single slot, model warnings taking priority.
- Extract useSelectExecutionTarget so the device switcher and the notice
share the local device-id resolution.
* 💄 style(chat-input): fix sandbox notice action spacing and alignment
Antd's alert section defaults to flex: 1, pushing the action button to
the far edge; the message line-height override targeted the wrong
class (.ant-alert-message instead of .ant-alert-title) so it never
applied; and @lobehub/ui's root style top-aligns children instead of
centering. Also bump the switch-to-local button to a primary type so
it reads as the notice's clear call to action.
* ✅ test(chat-input): add coverage for useSelectExecutionTarget
Cover boundDeviceId resolution order (cached gateway id -> async
fallback -> keep stale value on failure) and the heterogeneous-agent
guard that skips switching to local when no device can be resolved.
* 🐛 fix(chat-input): type ChatInputNotice key as literal union
t(notice.key) failed tsgo type-check (TS2345) since the feature's
original commit — key: string is too loose for i18next's typed
TFunction overloads, which require a literal key from the resources
union rather than plain string.
* ♻️ refactor(chat-input): derive ChatInputNotice type from resolveChatInputNotice
Replaces the hand-maintained ChatInputNotice interface with a type
derived from resolveChatInputNotice's actual return values (ReturnType +
`as const`). The manual interface had already drifted out of sync with
the implementation once (key: string vs. the literal keys actually
returned), causing a tsgo failure; deriving the type removes that
drift risk and tightens the union to only the key/type/action
combinations that can actually occur.
* 🐛 fix(chat): compare Immer draft via current() before deep-equal
fast-deep-equal comparing a live Immer draft proxy against a plain
merged object is fragile — its result depends on Immer's internal
Proxy trap implementation, which changed between immer 11.1.8 and
11.1.9 and made these no-op checks spuriously report a change.
* 👷 ci: shard Test Server into 2 jobs
Mirror Test App's shard+blob-report+merge pattern so server tests
run in parallel instead of one long single job.
* ✨ feat(agent-management): paginate searchAgent with real totals and cap notice
The searchAgent tool silently clamped limit to 20 with no pagination and
reported totalCount as the returned page size, so models (and users) could
never discover agents beyond the 20 most recently updated ones.
- AgentModel: extract shared where builder, add countAgents (same
conditions as queryAgents)
- lambda router + client agent service: expose countAgents
- server tool runtime & AgentManagerRuntime: pass offset through, report
real totals (workspace + marketplace), emit explicit notes when the
requested limit is capped and when more pages exist, explain
out-of-range offsets instead of claiming no matches
- manifest: add offset param, document pagination
- agent-manager-runtime: add vitest config + test scripts (suite was
previously unrunnable), repair stale store mocks
* 👷 build(ci): wire 8 tested packages into the package test workflow
An audit found 8 packages carrying test:coverage scripts that were never
added to the CI PACKAGES allowlist, so their suites never ran:
- agent-gateway-client, device-gateway-client, device-identity,
eval-dataset-parser: already green, added as-is
- eval-rubric, fetch-sse: had no package-level vitest config, so vitest
fell back to the root config whose setup/aliases break outside src/ —
added minimal configs
- heterogeneous-agents: one assertion drifted (labels registry gained
amp/hermes/openclaw/opencode) with nobody noticing — updated
- agent-manager-runtime: wired in the previous commit
All 8 verified locally with the exact CI command
(bun run --filter <pkg> test:coverage).
* ✅ test(agent-management): cover searchAgent error path and market totalCount fallback
Codecov flagged 3 uncovered lines in the patch: the searchAgents catch
block (2 misses) and the totalCount ?? items.length fallback (1 partial).
Add the missing failure-path and fallback tests on both execution paths
(client AgentManagerRuntime + server tool runtime).
* ✨ feat(agent-explorer): support multi-select delete in document tree
- Right-click on a multi-selected row deletes the whole selection; dedupe descendants when an ancestor folder is also selected
- Reserve chevron slot in SkillsList rows so atomic and bundled skills align
- Centralize EMPTY_ARRAY (typed `never[]`, frozen) in @lobechat/const
* ♻️ refactor: migrate delete confirm dialog from antd modal to confirmModal
* ✅ test: stabilize bun vitest environment
* 🔧 ci: avoid authenticated checkout for PR tests
* 👷 chore(ci): unify CI package manager from bun to pnpm
Replace bun with pnpm across all GitHub Actions workflows to ensure
lockfile consistency with pnpm-lock.yaml as single source of truth.
* 👷 chore(ci): replace bun run with pnpm run in package.json scripts
Fix build failure in CI where bun is not installed. Replace bun run
references in root and e2e package.json scripts with pnpm run.
* 👷 chore(e2e): replace bunx with npx in e2e server startup
* 👷 chore(ci): create unified setup-env action, use pnpm install + bun run
- Add .github/actions/setup-env composite action (pnpm + bun + node)
- Refactor desktop-build-setup to use setup-env internally
- All workflows: pnpm install for deps, bun run for scripts
- Revert package.json/e2e scripts back to bun run
- Remove all direct pnpm/action-setup and oven-sh/setup-bun from workflows
* 🐛 fix(test): inline lexical ESM deps for vitest under pnpm
pnpm's strict node_modules layout causes vitest ESM resolution to fail
for lexical's named exports. Add lexical and @lexical/* to inline deps.
* v2 init
* chore: update eslint suppressions and package dependencies
- Removed several eslint suppressions related to array sorting and reversing from eslint-suppressions.json to clean up the configuration.
- Updated @lobehub/lint package version from 2.0.0-beta.6 to 2.0.0-beta.7 in package.json for improvements and bug fixes.
- Made minor formatting adjustments in vitest.config.mts and various SKILL.md files for better readability and consistency.
Signed-off-by: Innei <tukon479@gmail.com>
* fix: clean up import statements and formatting
- Removed unnecessary whitespace in replaceComponentImports.ts for improved readability.
- Standardized import statements in contextEngineering.ts and createAgentExecutors.ts by adding missing spaces for consistency.
Signed-off-by: Innei <tukon479@gmail.com>
* chore: update eslint suppressions and clean up code formatting
* 🐛 fix: use vi.hoisted for mock variable initialization
Fix TDZ error in persona service test by using vi.hoisted() to ensure
mock variables are available when vi.mock factory runs.
---------
Signed-off-by: Innei <tukon479@gmail.com>
- Updated NODE_OPTIONS from 6144MB to 8192MB in Dockerfile, package.json scripts, GitHub workflows, and environment configurations.
- Ensured consistent memory allocation for builds and tests to improve performance.
Signed-off-by: Innei <tukon479@gmail.com>
* move
* refactor with model banks
* refactor with model banks
* refactor @/config/aiModels to model-bank
* refactor @/config/aiModels to model-bank
* fix model bank exports
* clean
* add test workflow
* try again
* fix
* add exports tests
* fix model bank alias
* Update tsconfig.json
* fix import issue
* clean unused code
* fix tests
* test workflow
* test workflow
* add test workflow
* add test workflow
* add test config
* add test config
* add test config
* add test config
* add test config
* update
* refactor tests
* fix tests
* fix tests
* exclude packages
* improve test
* fix test
* add a new package