basepeak-ai/node-gptscript
Watch
6
0
Fork
You've already forked node-gptscript
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(install): use v0.9.11 and soften token hints #4

Merged
thklein merged 1 commit from fix/install-v0.9.11 into main 2026-10-18 12:01:44 +00:00
Conversation 0 Commits 1 Files changed 5 +17 -15
thklein commented 2026-10-18 11:30:04 +00:00
Owner
Copy link

Summary

basepeak-ai/gptscript is public now and v0.9.11 is released, so the postinstall download works without a token.

  • Pin gptscript v0.9.11 in scripts/install-binary.js. The package version also moves to v0.9.11 (package.json, package-lock.json), matching the convention that the SDK version tracks the gptscript version.
  • Token stays optional. GPTSCRIPT_RELEASE_TOKEN is still sent as a Forgejo Authorization header when set. The comment no longer says the repo is private or that a token is required.
  • Better failure hint. Before, any failed download without a token told users to set GPTSCRIPT_RELEASE_TOKEN, even for network errors or timeouts. Now the token is suggested only when the host answers HTTP 401/403/404. Every other error is reported as is. The NODE_GPTSCRIPT_SKIP_INSTALL_BINARY hint is always printed.
  • README: says downloads are public and the token is optional.
  • CI: npm ci runs without GPTSCRIPT_RELEASE_TOKEN, so CI tests the anonymous install path that users take.

Verification

  • With no token set, node scripts/install-binary.js downloads v0.9.11 and bin/gptscript --version prints v0.9.11+7299ab79.
  • With the version changed to a release that does not exist, the installer prints The release host answered HTTP 404. If it requires authentication, set GPTSCRIPT_RELEASE_TOKEN ... and exits 1.
  • In a fresh scratch project with no token and npm_config_userconfig=/dev/null, npm install git+https://git.basepeak.dev/basepeak-ai/node-gptscript.git#fix/install-v0.9.11 installs the package, and node_modules/.bin/gptscript --version prints v0.9.11+7299ab79.
  • CI on this PR ran npm ci without a token, and the binary check printed gptscript version v0.9.11+7299ab79.
  • A slow link made one earlier attempt hit the installer's 300s download limit. It reported download did not finish within 300s and, as intended, did not suggest a token.
## Summary basepeak-ai/gptscript is public now and v0.9.11 is released, so the postinstall download works without a token. - **Pin gptscript v0.9.11** in `scripts/install-binary.js`. The package version also moves to `v0.9.11` (`package.json`, `package-lock.json`), matching the convention that the SDK version tracks the gptscript version. - **Token stays optional.** `GPTSCRIPT_RELEASE_TOKEN` is still sent as a Forgejo `Authorization` header when set. The comment no longer says the repo is private or that a token is required. - **Better failure hint.** Before, any failed download without a token told users to set `GPTSCRIPT_RELEASE_TOKEN`, even for network errors or timeouts. Now the token is suggested only when the host answers HTTP 401/403/404. Every other error is reported as is. The `NODE_GPTSCRIPT_SKIP_INSTALL_BINARY` hint is always printed. - **README**: says downloads are public and the token is optional. - **CI**: `npm ci` runs without `GPTSCRIPT_RELEASE_TOKEN`, so CI tests the anonymous install path that users take. ## Verification - With no token set, `node scripts/install-binary.js` downloads v0.9.11 and `bin/gptscript --version` prints `v0.9.11+7299ab79`. - With the version changed to a release that does not exist, the installer prints `The release host answered HTTP 404. If it requires authentication, set GPTSCRIPT_RELEASE_TOKEN ...` and exits 1. - In a fresh scratch project with no token and `npm_config_userconfig=/dev/null`, `npm install git+https://git.basepeak.dev/basepeak-ai/node-gptscript.git#fix/install-v0.9.11` installs the package, and `node_modules/.bin/gptscript --version` prints `v0.9.11+7299ab79`. - CI on this PR ran `npm ci` without a token, and the binary check printed `gptscript version v0.9.11+7299ab79`. - A slow link made one earlier attempt hit the installer's 300s download limit. It reported `download did not finish within 300s` and, as intended, did not suggest a token.
fix(install): use v0.9.11 and soften token hints
All checks were successful
test / test (pull_request) Successful in 21s
Details
ed27a4b100
 
The gptscript repo is public now, so release downloads work without a
token. Keep GPTSCRIPT_RELEASE_TOKEN as an optional auth header, but stop
calling the repo private and only suggest the token when the download
answers 401/403/404. Pin gptscript v0.9.11 and install it anonymously
in CI.
thklein deleted branch fix/install-v0.9.11 2026-10-18 12:01:44 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
basepeak-ai/node-gptscript!4
No description provided.