[FFI] In-process runtime (runtime.node) no longer published to npm as of CLI 1.0.85 — unobtainable for registry-mirrored builds
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 領域
- build-system, release
調査の方向性
Start by inspecting the platform package.json and the prebuilds//runtime.node path, then trace the build targets that use CopilotCliReleaseBaseUrl and the github-copilot--.tgz release asset. Done means the FFI runtime is obtainable through the npm registry mirror, either in the platform package or a lock-step runtime package; otherwise, document a supported route that does not require direct github.com access.
索引モデルが issue の本文から書いたものです。
説明
Summary
As of Copilot CLI 1.0.85 the platform npm package no longer contains the in-process (FFI) native runtime. It is published only as a GitHub release asset. Build environments that can reach an internal npm registry mirror but cannot make direct requests to github.com can therefore no longer obtain the FFI runtime at all, and are pinned to CLI 1.0.83 if they need in-process hosting.
What changed
Through 1.0.83, @github/copilot-<platform> shipped the whole package directory, including prebuilds/<platform>/runtime.node — the cdylib that RuntimeConnection.ForInProcess() loads. Its package.json declared no files field.
In 1.0.85 the manifest restricts the package contents:
"files": ["copilot.exe", "package.json", "README.md", "LICENSE.md"]
runtime.node is no longer present. It now ships only inside the release asset github-copilot-<version>-<platform>.tgz.
Correspondingly, GitHub.Copilot.SDK 1.0.14's build targets acquire the runtime bundle from exactly one source — CopilotCliReleaseBaseUrl, defaulting to https://github.com/github/copilot-cli/releases/download.
Why this is a problem
Enterprise build environments commonly restrict outbound network access to approved internal package feeds. Such feeds mirror package registries (npm, NuGet, PyPI, Maven, Cargo) through standard upstream configuration. They do not mirror arbitrary release assets, because release assets are not a package registry — there is no upstream type that can track and pull them automatically.
The practical consequences:
- stdio / child-process transport is fine. It needs only the CLI binary, which the slim npm package still provides. These consumers can track any future SDK version.
- In-process FFI is blocked at 1.0.85+. The cdylib cannot be obtained through any registry upstream.
This is sharper than a packaging inconvenience because of #2517: an access violation in the FFI JSON-RPC write path that kills the host process. I have measured that crash reproducing on runtime 1.0.83 and not reproducing on 1.0.85 under an identical harness. So the only FFI runtime reachable from a registry-mirrored environment is the one that still carries a process-killing bug, and the runtime that appears to fix it is unreachable.
The workaround available to affected consumers is to abandon in-process hosting and run the CLI as a child process — which gives up the performance and isolation properties that make the in-process transport attractive in the first place.
Ask
Publish the FFI native runtime to npm again, so it flows through standard registry upstreams with no special infrastructure. Either option works:
- Restore
prebuilds/<platform>/runtime.nodeto@github/copilot-<platform>, or - Publish it as its own package, e.g.
@github/copilot-runtime-<platform>, versioned in lock-step with the CLI, which keeps the default CLI package slim.
Option 2 seems to preserve whatever motivated the slim-down while unblocking FFI consumers.
If republishing to npm is not intended, could you document the supported story for consuming the FFI runtime without direct release-asset access? CopilotCliReleaseBaseUrl allows pointing at a mirror, but populating that mirror still requires fetching the release assets from somewhere, which is the step these environments cannot perform.
Environment
GitHub.Copilot.SDK1.0.13 (CLI 1.0.83) and 1.0.14 (CLI 1.0.85)- .NET 8, Windows x64 and Linux x64 containers
- Build agents restricted to an internal npm registry mirror; no direct
github.comegress
- 主要言語
- TypeScript
- スター
- 10.5k
- フォーク
- 1.5k
- 平均マージ
- 1日 7時間
- マージ済み PR（30日）
- 64
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
github/copilot-sdk のほかの issue
-
Clarify SDK architecture and in-process runtime transport対応中かも @KalebCole が 4 日前に担当しました。 オープンdocumentation
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
github/copilot-sdk#2804 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Python ModelLimits drops max_output_tokens from model metadata対応中かも @HDMowri が 5 日前に担当しました。 オープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
github/copilot-sdk#2798 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
github/copilot-sdk#2793 ·
メンテナーはふだん 1 日以内に返信
-
agentic-workflows
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
github/copilot-sdk#2782 ·
メンテナーはふだん 1 日以内に返信
-
Rust: subagent lifecycle hooks are logged as unknown対応中かも @hackberry-lab が 8 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
github/copilot-sdk#2781 ·
メンテナーはふだん 1 日以内に返信
github/copilot-sdk の issue をすべて見る
似ている issue
-
Link Checker Reportオープンautomated issue report
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
databendlabs/databend-docs#3511 ·
-
area/dashboard kind/bug QA/dev-automation
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
rancher/dashboard#19379 · コメント 2 件 ·
メンテナーはふだん 5 日以内に返信
-
perf(core): getComments() runs the approved count and the comment list as two sequential queriesオープンarea/core bot:bug bot:working
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
emdash-cms/emdash#3905 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
lingdojo/kana-dojo#31728 · コメント 1 件 · リアクション 5 件 ·
メンテナーはふだん 1 日以内に返信
-
selective-claw: freshTailTurns=0 keeps ALL turns verbatim and summarizes none (slice(-0) === slice(0))対応中かも @zjncs が今日担当しました。 オープンcomponent:tokenless
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
agentic-os-org/ANOLISA#6112 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信