ci: publish gptscript releases to Forgejo only #19

Merged
thklein merged 2 commits from ci/forgejo-release into main 2026-10-17 20:51:14 +00:00
Owner

Releases now publish only to this Forgejo repo. Nothing goes to GitHub, Homebrew, winget or R2 any more.

  • .goreleaser.yml:
    • Attaches the archives and checksums.txt to the git.basepeak.dev release of the tag (gitea_urls, force_token: gitea).
    • Removes the brews section.
    • Fixes the goreleaser v2 deprecations.
  • release.yaml:
    • A single job runs goreleaser v2.18.3 through the Go module proxy, using the automatic token.
    • The winget job and the dispatches to the archived upstream repos are removed.
  • Removed main.yaml and push-quickstart.yaml, which uploaded to the upstream's R2 bucket, and dependabot-reviewers.yaml, which only works on GitHub.

Archive names are unchanged (gptscript-vX.Y.Z-{linux-amd64,linux-arm64,macOS-universal}.tar.gz, -windows-{amd64,arm64}.zip), so node-gptscript's postinstall only needs a new base URL.

Verified with goreleaser check and a local release --snapshot --clean, which produced all five archives and the checksums.

After merge, tag v0.9.10 (bpai already pins a v0.9.10 pseudo-version) to cut the first Forgejo release.

Releases now publish only to this Forgejo repo. Nothing goes to GitHub, Homebrew, winget or R2 any more. - `.goreleaser.yml`: - Attaches the archives and `checksums.txt` to the git.basepeak.dev release of the tag (`gitea_urls`, `force_token: gitea`). - Removes the brews section. - Fixes the goreleaser v2 deprecations. - `release.yaml`: - A single job runs goreleaser v2.18.3 through the Go module proxy, using the automatic token. - The winget job and the dispatches to the archived upstream repos are removed. - Removed `main.yaml` and `push-quickstart.yaml`, which uploaded to the upstream's R2 bucket, and `dependabot-reviewers.yaml`, which only works on GitHub. Archive names are unchanged (`gptscript-vX.Y.Z-{linux-amd64,linux-arm64,macOS-universal}.tar.gz`, `-windows-{amd64,arm64}.zip`), so node-gptscript's postinstall only needs a new base URL. Verified with `goreleaser check` and a local `release --snapshot --clean`, which produced all five archives and the checksums. After merge, tag `v0.9.10` (bpai already pins a v0.9.10 pseudo-version) to cut the first Forgejo release.
Tags now build with goreleaser and attach the archives to the
git.basepeak.dev release. node-gptscript downloads the binary from
there. The Homebrew tap, winget and the dispatches to the archived
upstream repos are gone, and goreleaser comes pinned through the Go
module proxy.
ci: drop workflows that publish outside Forgejo
Some checks failed
Request reviewers for Dependabot PRs / request_reviewers (pull_request_target) Has been skipped
smoke / check-label (pull_request_target) Failing after 2s
smoke / gpt-4o-2024-08-06 (pull_request_target) Has been skipped
smoke / gpt-4o-mini-2024-07-18 (pull_request_target) Has been skipped
smoke / claude-3-7-sonnet-20250219 (pull_request_target) Has been skipped
test / test (ubuntu-22.04) (pull_request) Failing after 11s
Validate docs build / validate-docs (pull_request) Failing after 20s
integration / integration (windows-latest) (pull_request) Has been cancelled
test / test (windows-latest) (pull_request) Has been cancelled
integration / integration (ubuntu-22.04) (pull_request) Has been cancelled
9d87901b09
main and push-quickstart uploaded snapshots and install.sh to the
archived upstream's R2 bucket; dependabot-reviewers only works on
GitHub.
thklein deleted branch ci/forgejo-release 2026-10-17 20:51:15 +00:00
Sign in to join this conversation.
No reviewers
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/gptscript!19
No description provided.