Skip to content

fix: address upstream CI/build issues (#782 #783 #784) - #785

Open
YOMXXX wants to merge 4 commits into
TencentCloud:feat/server_teamfrom
YOMXXX:fix/782-783-784-upstream-fixes
Open

fix: address upstream CI/build issues (#782 #783 #784)#785
YOMXXX wants to merge 4 commits into
TencentCloud:feat/server_teamfrom
YOMXXX:fix/782-783-784-upstream-fixes

Conversation

@YOMXXX

@YOMXXX YOMXXX commented Aug 4, 2026

Copy link
Copy Markdown

Fixes #782, #783, #784 — three upstream issues, plus the dead build:seed-v2 that blocks CI on the release branch.

#782 — CI never runs on PRs to feat/server_team

pr-ci.yml only triggered on PRs to main, but the default/release branch is feat/server_team. Trigger on both branches so pack validation, manifest checks, size guard, and skill-isolation guard actually run on PRs.

#783main / bin launchers point at dist/server.js (tsdown emits .mjs)

  • package.json main./dist/server.mjs
  • bin/server.mjsimport "../dist/server.mjs"
  • bin/mcp.mjsimport "../dist/mcp/server.mjs"

npm consumers and knowledge-server / knowledge-mcp bins now resolve the real build output.

#784typecheck fails in response-envelope.ts

bodyCache.text is typed string in Hono but holds a Promise at runtime. Cast the cached value (as unknown as string) to keep runtime behaviour and fix the TS error.

(extra) — dead build:seed-v2 breaks CI Pack

With CI now enabled (#782), the Pack job surfaced a pre-existing build break: build:scripts still runs build:seed-v2, which references the removed scripts/seed-v2/ (TS5058). Dropped the dead script so this branch's CI is green (same change as #775, needed here because #782 now triggers CI on feat/server_team).

Verification

  • MemoryKnowledge: npm run build → emits dist/server.mjs; npm run typecheck → exit 0
  • node --check on both bin launchers
  • pr-ci.yml parses with branches: ["main", "feat/server_team"]
  • MemoryCore: npm run build:scripts passes (seed-v2 removed)

@Maxwell-Code07

Copy link
Copy Markdown
Collaborator

Thanks for your attention! We will schedule an internal review as soon as possible.

YOMXXX added 4 commits August 5, 2026 18:13
pr-ci.yml only triggered on PRs to main, but the repo's default/release
branch is feat/server_team, so every PR there skipped CI entirely (pack
validation, manifest checks, size guard, skill-isolation guard). Trigger
on both branches.

Fixes TencentCloud#782

Signed-off-by: 李冠辰 <liguanchen@xiaomi.com>
package.json main was "./dist/server.js" and bin/server.mjs /
bin/mcp.mjs imported "../dist/server.js", but tsdown (ESM +
fixedExtension) emits dist/server.mjs — the .js files do not exist, so npm
consumers and the knowledge-server / knowledge-mcp bins failed.

Fixes TencentCloud#783

Signed-off-by: 李冠辰 <liguanchen@xiaomi.com>
bodyCache.text is typed string in Hono but holds a Promise at runtime
(c.req.text() calls .then()). Cast the cached value to keep runtime
behaviour while fixing the TS error.

Fixes TencentCloud#784

Signed-off-by: 李冠辰 <liguanchen@xiaomi.com>
The Pack CI job fails on the release branch with "TS5058:
scripts/seed-v2/tsconfig.json does not exist" because build:scripts still
references the removed seed-v2 directory. Drop the dead script so this
branch's CI is green (same change as TencentCloud#775; needed here because TencentCloud#782 now
triggers CI on feat/server_team).

Part of TencentCloud#759

Signed-off-by: 李冠辰 <liguanchen@xiaomi.com>
@YOMXXX
YOMXXX force-pushed the fix/782-783-784-upstream-fixes branch from 2cf4f9f to 83c6a3b Compare August 5, 2026 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI never runs on PRs to feat/server_team (pr-ci.yml only triggers on main)

2 participants