Skip to content

Add Scoop bucket manual-update Justfile recipe#16

Open
johnpmitsch wants to merge 1 commit into
mainfrom
add/scoop-bucket-recipe
Open

Add Scoop bucket manual-update Justfile recipe#16
johnpmitsch wants to merge 1 commit into
mainfrom
add/scoop-bucket-recipe

Conversation

@johnpmitsch

Copy link
Copy Markdown
Collaborator

Summary

Adds release-update-scoop-bucket — the Scoop equivalent of release-update-homebrew-tap we shipped with Phase 3. A maintainer-run command that downloads the Windows zip's sha256 from a release and writes a Scoop manifest (bucket/qn.json) into a local clone of quicknode/scoop-bucket, then prints the git push command.

The manifest includes checkver = \"github\" and an autoupdate block, so once a user has tapped the bucket, scoop update finds new versions on its own — we only need to run this recipe to keep the canonical version field honest for scoop search.

Like the Homebrew recipe, this stays manual until we have a SCOOP_BUCKET_TOKEN PAT to automate the push. At that point we'll add a publish-scoop workflow modeled on publish-deb.

Usage

just release-update-scoop-bucket 0.1.4 ~/qn/scoop-bucket

Test plan

  • Recipe parses (just --list shows it).
  • End-to-end-tested against a throwaway git repo with v0.1.4's actual release: generated a valid JSON manifest with the real sha256, correct binary name, and an autoupdate block whose $version placeholder is preserved unexpanded.
  • After merge, manually create quicknode/scoop-bucket (empty public repo), clone it, run the recipe against v0.1.4, push.
  • README install matrix add scoop install quicknode/qn (or quicknode-cli) entry once the bucket is populated.

Mirrors release-update-homebrew-tap: a maintainer-run command that
syncs a Scoop manifest to a local clone of quicknode/scoop-bucket.
Until we have a SCOOP_BUCKET_TOKEN PAT to automate the push, this is
the manual path.

The generated bucket/qn.json includes `checkver = "github"` and an
`autoupdate` block, so once a user has tapped the bucket, `scoop
update` finds new versions on its own — no recurring manual push
needed for every release. We still run the recipe to bump the
canonical `version` field (so `scoop search qn` is honest about what's
current) and to surface the hash for offline verification.

Usage:

  just release-update-scoop-bucket 0.1.4 ~/qn/scoop-bucket

The recipe downloads the Windows zip's sha256 sidecar from the
GitHub release, renders the manifest with the version and hash
substituted, commits with a clean message, and prints the git push
command (it does not push automatically — the maintainer reviews
and pushes themselves).

When SCOOP_BUCKET_TOKEN exists we'll add a CI publish-scoop workflow
modeled on publish-deb, and this recipe becomes a manual-recovery
fallback.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant