Conversation
Add a publish-packaging job to the tag workflow: after the installers are on the Release, it downloads the artifacts, computes their sha256, and stamps the packaging/ manifests to the new version — pushing the Homebrew cask and Scoop manifest to their tap/bucket repos and publishing the AUR dogwalker-bin package. Each channel is guarded by its secret (PACKAGING_TOKEN; AUR_SSH_PRIVATE_KEY / AUR_USERNAME / AUR_EMAIL), so it's a no-op until they're configured. Documents the one-time setup in packaging/README.md and updates the AGENTS release guide. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The publish-packaging steps used `if: secrets.X != ''`, which is not a valid context in a step `if` and made GitHub reject the whole workflow. Fold the presence check into job-level env booleans (secrets are allowed in job env) and gate the steps on those. Co-Authored-By: Claude Opus 4.8 <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.
Wire the package-manager channels into the tag-based CD.
What
A new
publish-packagingjob in.github/workflows/build.ymlruns after the tag build attaches every OS's installers to the Release. It:.debfrom the Release and computes theirsha256.packaging/manifests to the new version and pushes:caribeedu/homebrew-dogwalker(Casks/dogwalker.rb)caribeedu/scoop-bucket(bucket/dogwalker.json)dogwalker-bin→ viaKSXGitHub/github-actions-deploy-aurGuarded — safe by default
Each channel step is skipped unless its secret is set, so the job is a green no-op until setup is done (the release itself is never affected):
PACKAGING_TOKEN— PAT with contents:write on the tap + bucket repos (Homebrew + Scoop).AUR_SSH_PRIVATE_KEY,AUR_USERNAME,AUR_EMAIL— the AUR publish.What you need to do (one-time)
homebrew-dogwalkerandscoop-bucket, and claim the AURdogwalker-bin(account + SSH key).Full details in
packaging/README.md. No app-code changes — CI/docs only.🤖 Generated with Claude Code