fix(install): fetch gptscript from our Forgejo release #1

Merged
thklein merged 4 commits from fix/forgejo-only into main 2026-10-17 21:25:52 +00:00
Owner

gptscript now comes from our Forgejo release, and nothing is published to PyPI or GitHub any more.

  • gptscript/install.py and scripts/package (wheel staging):
    • Download our fork's v0.9.10 from git.basepeak.dev/basepeak-ai/gptscript/releases/download/ instead of upstream v0.9.8 on GitHub.
    • Authenticate with GPTSCRIPT_RELEASE_TOKEN, since the repo is private.
    • Use (10s connect, 30s read) timeouts.
    • Fail on HTTP errors. Previously the error page was written to disk as the archive.
    • install.py fails if the archive has no binary.
  • pyproject.toml: version 0.9.10, and project URLs point to Forgejo.
  • Workflows:
    • Removed the PyPI upload, the GitHub dispatch bump, the dependabot hook, and the GitHub permission check plus reusable workflow, which Forgejo rejects.
    • One test.yaml installs gptscript through install.py using the org read token, and runs tox only when provider keys exist. The org currently has none.
gptscript now comes from our Forgejo release, and nothing is published to PyPI or GitHub any more. - `gptscript/install.py` and `scripts/package` (wheel staging): - Download our fork's `v0.9.10` from `git.basepeak.dev/basepeak-ai/gptscript/releases/download/` instead of upstream v0.9.8 on GitHub. - Authenticate with `GPTSCRIPT_RELEASE_TOKEN`, since the repo is private. - Use (10s connect, 30s read) timeouts. - Fail on HTTP errors. Previously the error page was written to disk as the archive. - `install.py` fails if the archive has no binary. - `pyproject.toml`: version 0.9.10, and project URLs point to Forgejo. - Workflows: - Removed the PyPI upload, the GitHub dispatch bump, the dependabot hook, and the GitHub permission check plus reusable workflow, which Forgejo rejects. - One `test.yaml` installs gptscript through `install.py` using the org read token, and runs tox only when provider keys exist. The org currently has none.
install.py and scripts/package downloaded upstream gptscript v0.9.8 from
GitHub with no timeout and wrote whatever came back. Fetch our fork's
v0.9.10 from git.basepeak.dev instead, authenticated through
GPTSCRIPT_RELEASE_TOKEN (the repo is private), with connect/read
timeouts. HTTP errors and archives without the binary now fail.
ci: stop publishing to PyPI and GitHub
Some checks failed
Request reviewers for Dependabot PRs / request_reviewers (pull_request_target) Has been skipped
pull_request.yaml / ci: stop publishing to PyPI and GitHub (pull_request_target) Failing after 0s
test / test (pull_request) Has been cancelled
92deb9e6ba
Drop the PyPI upload on tags, the GitHub repository_dispatch bump and
the dependabot hook. One Forgejo test workflow replaces the GitHub
permission check and reusable workflow: it installs gptscript through
install.py and runs tox only when provider keys exist.
ci: run the installer by path and pass its token to tox
Some checks failed
pull_request.yaml / ci: run the installer by path and pass its token to tox (pull_request_target) Failing after 0s
test / test (pull_request) Has started running
5b2b6f4d84
python -m gptscript.install imports the package, whose httpx dep is
not in requirements.txt. tox re-runs install_gptscript in its own env,
so it needs GPTSCRIPT_RELEASE_TOKEN passed through as well.
ci: re-run after runner MTU fix
Some checks failed
pull_request.yaml / ci: re-run after runner MTU fix (pull_request_target) Failing after 0s
test / test (pull_request) Successful in 38s
7b1c1433f0
thklein deleted branch fix/forgejo-only 2026-10-17 21:25:52 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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!1
No description provided.