feat: distribute the CLI via Scoop - #691
Draft
NickJosevski wants to merge 1 commit into
Draft
Conversation
Serves Scoop from a bucket repo we own, OctopusDeploy/scoop-octopus, as the official ScoopInstaller/Main bucket only accepts widely-adopted tools. As with the homebrew tap, goreleaser writes the manifest and the Octopus deployment process commits it into the bucket. The manifest covers 64bit and arm64, making Scoop the only Windows package manager through which we ship a native ARM build. Closes the last unticked box on #37. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #37 — Scoop was the last unticked box on the package manager list.
Change
Adds a
scoopsblock to.goreleaser.yamland a deployment process step that pushes the generated manifest.Scoop is served from a bucket repository we own, OctopusDeploy/scoop-octopus, rather than the official
ScoopInstaller/Mainbucket, which only accepts widely-adopted tools (500+ stars, 150+ forks). This mirrors the homebrew tap: goreleaser generates the manifest butskip_uploadstops it publishing, and the Octopus deployment process commits it intobucket/.Unlike the homebrew step, the scoop step commits straight to the default branch instead of raising a PR — a bucket is machine-maintained, there is nothing for a human to review.
The manifest covers both
64bitandarm64, so Scoop becomes the only Windows package manager through which we ship a native ARM build (winget and chocolatey are x64 only).Why draft
The bucket repository has to exist, and
Publish:Scoop:Username,Publish:Scoop:UserEmailandPublish:Scoop:ApiKeyhave to be set on the Octopus project, before this can be merged. Nothing here is verifiable end to end until a release runs.🤖 Generated with Claude Code