Repository navigation
feat(scoop): Add a Scoop bucket and release-time package metadata automation - #49
Merged
Merged
Conversation
Install the stable Windows x64 and ARM64 release archives through Scoop with pinned SHA-256 checksums and SHA256SUMS-based autoupdate hash extraction. Document installation, Scoop-managed upgrades, and manifest maintenance in the current README, mirroring the Homebrew tap. Validated the manifest JSON with jq, both hash extraction patterns against the published v0.1.20 SHA256SUMS, and a full download of termgram-0.1.20-windows.zip whose SHA-256 matches the pinned value. Amp-Thread-ID: https://ampcode.com/threads/T-01a0c24b-d4c2-707c-86c1-da9f060dd6b7 Co-authored-by: Amp <amp@ampcode.com>
Regenerate Formula/termgram.rb and bucket/termgram.json from the release's SHA256SUMS after publishing the latest stable release in a plan, commit the metadata with a chore(release) subject, and push it to the default branch. Prerelease-only plans leave the pinned versions untouched, and an unchanged manifest skips the commit so idempotent republishes stay silent. Remove the now-redundant Maintaining Homebrew and Maintaining Scoop README sections, and match the manifest description with the formula's. Validated the workflow YAML and its shell syntax, reproduced the committed formula byte-for-byte from the published v0.1.20 SHA256SUMS, verified both autoupdate hash-extraction patterns against those checksums, and simulated the update flow for the pinned and a next version. Amp-Thread-ID: https://ampcode.com/threads/T-01a0c24b-d4c2-707c-86c1-da9f060dd6b7 Co-authored-by: Amp <amp@ampcode.com>
Contributor
Author
Read checksums from the latest published stable release independently of this CI run's release plan. Rebuilt archives can differ from bytes already published by an overlapping run, and later plans omit published versions. Apply generated metadata on the current default branch in an isolated worktree, retry ordinary pushes when the branch advances, and skip commits when the remote already contains the expected metadata. This also repairs missed updates during prerelease-only or empty plans. Add CI regression coverage for published checksums, reruns, missing stable releases, and concurrent branch updates. Validate shell/workflow syntax and reproduce the pinned manifests using the published v0.1.20 checksums.
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
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.
Summary
Add an in-repository Scoop bucket for Windows x64 and ARM64 installs, alongside the existing Homebrew tap. Keep both package managers on the latest published stable release automatically.
Changes
bucket/termgram.json, pinned to v0.1.20 with the release's SHA-256 checksums andSHA256SUMS-based autoupdate extraction.scripts/update-package-metadata.py, validating coverage of all six platform archives.SHA256SUMS, so overlapping rebuilds cannot substitute unpublished archive hashes.chore(release):subject so metadata commits do not create another stable release.Validation
SHA256SUMSreproduces both committed manifests byte-for-byte; JSON and Ruby syntax checks pass.