Commit 9ac6a48
committed
Embed @napi-rs/keyring native bindings for all CLI release targets
The CLI publish workflow cross-compiles all six bun targets on one Linux
host after a single `bun install`. @napi-rs/keyring ships its native
binding as os/cpu-gated platform packages, so that install only fetches
the host's (@napi-rs/keyring-linux-x64-gnu). bun --compile embeds a
binding only when its platform package is present on disk, so every
non-linux-x64 binary shipped with no binding and silently fell back to
plaintext credential storage at runtime (the keyring code itself landed
earlier; this is the missing build half).
Fetch each target's platform package (direct npm tarball, which bypasses
the os/cpu install skip) before cross-compiling so every released binary
embeds its native keyring binding.1 parent 3ffded3 commit 9ac6a48
1 file changed
Lines changed: 12 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
46 | 46 | | |
47 | 47 | | |
48 | 48 | | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
49 | 61 | | |
50 | 62 | | |
51 | 63 | | |
| |||
0 commit comments