ci: publish gptscript releases to Forgejo only #19
No reviewers
Labels
No labels
area/engine
clarity/clear
enhancement
security
size/M
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
basepeak-ai/gptscript!19
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/forgejo-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Releases now publish only to this Forgejo repo. Nothing goes to GitHub, Homebrew, winget or R2 any more.
.goreleaser.yml:checksums.txtto the git.basepeak.dev release of the tag (gitea_urls,force_token: gitea).release.yaml:main.yamlandpush-quickstart.yaml, which uploaded to the upstream's R2 bucket, anddependabot-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 checkand a localrelease --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.