Skip to content

Fix/ci pnpm lockfile - #1

Open
simoncheungbg wants to merge 3 commits into
mainfrom
fix/ci-pnpm-lockfile
Open

simoncheungbg wants to merge 3 commits into
mainfrom
fix/ci-pnpm-lockfile

Conversation

@simoncheungbg

Copy link
Copy Markdown
Contributor
  1. 文档小修复
  2. github action修复

simoncheungbg and others added 3 commits May 29, 2026 13:48
Restores the canonical portal repo name. The publishable npm package is
still bitget-agent-installer, but it lives in the bitget/agent-hub
repository (alongside docs, assets, e2e tests). The earlier rename of
the repo folder to agent-installer was incorrect — the folder serves
the broader portal role and should retain its agent-hub name.
The lockfile was missing after splitting this package out of the
monorepo, causing CI to fail at actions/setup-node@v4 (cache: pnpm)
and at `pnpm install --frozen-lockfile`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… localhost

Tests were pointing BITGET_API_BASE_URL at http://localhost:<port>, but
MockServer binds only to 127.0.0.1. On Node 18+ with verbatim DNS lookup
(default), GitHub Actions Ubuntu runners resolve `localhost` to ::1
first, so fetch hits IPv6 and the server isn't there — surfaced as
"Failed to call Bitget endpoint ..." NetworkError.

- MockServer now exposes a `baseUrl` getter that returns the actual
  127.0.0.1:<port> it bound to, eliminating URL-construction mismatch.
- All 5 test files use `server.baseUrl` instead of building their own.

This also benefits external SDK consumers using the published
`bitget-agent-sdk/testing` MockServer, who'd otherwise hit the same
trap on Linux CI.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@simoncheungbg simoncheungbg self-assigned this Jun 1, 2026
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.

1 participant