basepeak-ai/py-gptscript
Watch
6
0
Fork
You've already forked py-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:46 +00:00
Conversation 0 Commits 1 Files changed 5 +28 -17
thklein commented 2026-10-18 11:30:14 +00:00
Owner
Copy link

Summary

basepeak-ai/gptscript is public now and v0.9.11 is released, so install_gptscript and scripts/package download it without a token.

  • Pin gptscript v0.9.11 in gptscript/install.py and scripts/package. The package version also moves to 0.9.11 (pyproject.toml), 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 (tox still passes it through). The comments no longer say the repo is private.
  • Better failure hint. Before, any non-2xx answer without a token added "set GPTSCRIPT_RELEASE_TOKEN for the private gptscript repo". Now the token is suggested only on HTTP 401/403/404. Other statuses report just the status.
  • README: says downloads are public and the token is optional.
  • CI: the workflow no longer sets GPTSCRIPT_RELEASE_TOKEN, so both install runs (the direct run and the one in tox) test the anonymous path.

Verification

In a fresh Python 3.12 venv with no token in the environment and PIP_CONFIG_FILE=/dev/null:

pip install git+https://git.basepeak.dev/basepeak-ai/py-gptscript.git@fix/install-v0.9.11   # gptscript 0.9.11
install_gptscript    # symlink -> venv/bin/gptscript-v0.9.11
gptscript --version  # gptscript version v0.9.11+7299ab79
## Summary basepeak-ai/gptscript is public now and v0.9.11 is released, so `install_gptscript` and `scripts/package` download it without a token. - **Pin gptscript v0.9.11** in `gptscript/install.py` and `scripts/package`. The package version also moves to `0.9.11` (`pyproject.toml`), 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 (tox still passes it through). The comments no longer say the repo is private. - **Better failure hint.** Before, any non-2xx answer without a token added "set GPTSCRIPT_RELEASE_TOKEN for the private gptscript repo". Now the token is suggested only on HTTP 401/403/404. Other statuses report just the status. - **README**: says downloads are public and the token is optional. - **CI**: the workflow no longer sets `GPTSCRIPT_RELEASE_TOKEN`, so both install runs (the direct run and the one in tox) test the anonymous path. ## Verification In a fresh Python 3.12 venv with no token in the environment and `PIP_CONFIG_FILE=/dev/null`: ``` pip install git+https://git.basepeak.dev/basepeak-ai/py-gptscript.git@fix/install-v0.9.11 # gptscript 0.9.11 install_gptscript # symlink -> venv/bin/gptscript-v0.9.11 gptscript --version # gptscript version v0.9.11+7299ab79 ```
fix(install): use v0.9.11 and soften token hints
All checks were successful
test / test (pull_request) Successful in 22s
Details
91e4cab859
 
The gptscript repo is public now, so release downloads work without a
token. Keep GPTSCRIPT_RELEASE_TOKEN as an optional auth header in
install.py and scripts/package, but stop calling the repo private and
only suggest the token on HTTP 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:46 +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/py-gptscript!4
No description provided.