larksuite / larksuite/cli

Request Windows binary release

Open
#107 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

domain/core enhancement
Dominant language
Go
Stars
17.3k
Forks
1.4k
Avg merge
2d 4h
Merged PRs (30d)
105

Description

Request: Add Windows (win32) binary release\n\n### Problem\nThe current GitHub release (v1.0.0) only contains macOS and Linux binaries. The Windows platform is not supported.\n\nWhen installing via npm (

pm install -g @larksuite/cli) on Windows, the install script attempts to download lark-cli-1.0.0-windows-amd64.zip from the release page, but this file does not exist, resulting in a 404 error followed by connection timeout.\n\n### Evidence\n- Release assets only contain: lark-cli-1.0.0-darwin-amd64.tar.gz, lark-cli-1.0.0-darwin-arm64.tar.gz, lark-cli-1.0.0-linux-amd64.tar.gz\n- No lark-cli-1.0.0-windows-amd64.zip\n\n### Why this matters\nWindows is a major platform for development and AI agent workflows. Without a pre-built binary, Windows users must build from source (requiring Go 1.23+), which is a significant barrier.\n\n### Request\nPlease add Windows binary to the CI/CD release pipeline. The install script already supports win32 (see scripts/install.js platform mapping), so it should be straightforward to add a Windows build step.\n\n### Additional context\n- Node.js version: v24.14.0 (Windows x64)\n- Platform: Windows_NT 10.0.22631\n

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading scripts/install.js and the existing release pipeline that produces the macOS and Linux assets. Trace how the Windows platform maps to its archive name, then verify that a Windows amd64 release asset is produced and that npm installation on Windows no longer receives a 404.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, node.js
Domain
ci-cd, release
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
67/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.