Skip to content

ci: drop lockfile requirement so workflows can run without pnpm-lock.… - #1

Open
simoncheungbg wants to merge 2 commits into
mainfrom
fix/add-pnpm-lockfile
Open

simoncheungbg wants to merge 2 commits into
mainfrom
fix/add-pnpm-lockfile

Conversation

@simoncheungbg

Copy link
Copy Markdown
Contributor

No description provided.

simoncheungbg and others added 2 commits June 1, 2026 12:59
…yaml

The repo never committed a pnpm-lock.yaml, so `cache: pnpm` in
actions/setup-node and `pnpm install --frozen-lockfile` both fail with
"Dependencies lock file is not found". Remove the cache directive and
switch to --no-frozen-lockfile in both ci.yml and release.yml.

The cleaner alternative — committing pnpm-lock.yaml — requires running
`pnpm install --lockfile-only --ignore-scripts` in an env with access
to bitget-agent-sdk; that can land as a follow-up PR.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Skill runtime depends on the bgc CLI binary, not the bitget-agent-sdk
npm package. The drift check existed only because gen-references.js
auto-generates references/commands.md from SDK tool defs — that is a
maintainer-side concern, not something CI needs to enforce on every
PR. references/commands.md is committed, and prepublishOnly regenerates
it at npm publish time, so the deliverable cannot ship stale.

Validate now only runs the SKILL.md frontmatter check, which does not
need the SDK or pnpm at all.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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