jeopi-cli 16.2.17 → 16.2.19
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -0
- package/dist/cli.js +2231 -2231
- package/dist/types/cli/update-cli.d.ts +26 -1
- package/package.json +12 -12
- package/src/cli/update-cli.ts +50 -18
- package/src/internal-urls/docs-index.generated.txt +1 -1
- package/src/main.ts +2 -15
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,19 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [16.2.19] - 2026-07-02
|
|
6
|
+
|
|
7
|
+
### Fixed
|
|
8
|
+
|
|
9
|
+
- Fixed the startup update notice never appearing: the version check queried the nonexistent `jeopi` npm package (renamed CLI ships as `jeopi-cli`), so the 404 silently suppressed the "New version X is available" banner. The check now shares the updater's `NPM_PACKAGE`/`NPM_REGISTRY` constants so the notice and `jeopi update` can never target different packages.
|
|
10
|
+
- Fixed Windows npm installs never finding a prebuilt native addon: the npm registry's name heuristic rejects `jeopi-natives-win32-x64` as spam, so the win32 leaf now publishes under the `jeopi-natives-windows-x64` alias. The native loader probes the alias first (falling back to the tag-derived name), and `jeopi update` pins the aliased leaf in lock-step with `jeopi-natives`.
|
|
11
|
+
|
|
12
|
+
## [16.2.18] - 2026-07-02
|
|
13
|
+
|
|
14
|
+
### Fixed
|
|
15
|
+
|
|
16
|
+
- Fixed release CI after the jeopi rebrand by asserting the raw SSE dropped-record debug marker uses `jeopi-debug-dropped`.
|
|
17
|
+
|
|
5
18
|
## [16.2.17] - 2026-07-02
|
|
6
19
|
|
|
7
20
|
### Changed
|