fix: support PR review for fork-based pull requests · lishuceo/anycode@a7134be

Error: [vitest] No "buildCombinedProgressCard" export is defined on the "../message-builder.js" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("../message-builder.js"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ ensureThread src/feishu/thread-utils.ts:43:16 ❯ src/feishu/__tests__/thread-utils.test.ts:120:28

src/feishu/__tests__/thread-utils.test.ts > ensureThread > without rootId (new message in main chat) > should create a new thread and return greeting message ID: src/feishu/thread-utils.ts#L43

Error: [vitest] No "buildCombinedProgressCard" export is defined on the "../message-builder.js" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("../message-builder.js"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ ensureThread src/feishu/thread-utils.ts:43:16 ❯ src/feishu/__tests__/thread-utils.test.ts:89:28

src/feishu/__tests__/thread-utils.test.ts > ensureThread > with rootId (user replies in existing thread) > should treat rootId without threadId as main chat quote-reply (not a thread): src/feishu/thread-utils.ts#L43

Error: [vitest] No "buildCombinedProgressCard" export is defined on the "../message-builder.js" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("../message-builder.js"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ ensureThread src/feishu/thread-utils.ts:43:16 ❯ src/feishu/__tests__/thread-utils.test.ts:74:28

docs-scope

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

test

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

test: src/__tests__/ask-user-question.test.ts#L169