Enhance release process with security hardening and package distribution - #6
Merged
Conversation
Add GoReleaser homebrew_casks and scoops sections targeting the IvMisticos/homebrew-tap and IvMisticos/scoop-bucket repos, wire up the TAP_GITHUB_TOKEN secret in the release workflow, and update the README install instructions. Also trim redundant README content and fix typos. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RZdU2QLP9bW65wiHKsaNaT
- Require manual approval via the `release` GitHub Actions environment before the release job runs; drop the draft release in favour of it. - Pin all actions to commit SHAs to prevent tag-mutation supply-chain attacks against the secret-bearing job. - Default top-level permissions to none; grant `contents: write` only to the release job. - Add step-security/harden-runner (egress audit, disable sudo) and persist-credentials: false on checkout. - Add concurrency guard so two releases can't run for the same ref. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RZdU2QLP9bW65wiHKsaNaT
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
2 participants
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
This PR significantly improves the release workflow and distribution capabilities by implementing security best practices in the GitHub Actions release pipeline and adding support for Homebrew and Scoop package managers.
Key Changes
GitHub Actions Workflow Security (
goreleaser.yaml)contents: writeto empty{}, granting only necessary permissions per-jobenvironment: releaseto require manual approval before releases, with environment-specific secrets for enhanced securitystep-security/harden-runneraction with egress audit policy to detect unexpected network callsGITHUB_TOKEN, using environment variables and API insteadTAP_GITHUB_TOKENenvironment secret scoped only to homebrew-tap and scoop-bucket repositoriesRelease Configuration (
goreleaser.yaml)homebrew_casksconfiguration to distribute binaries via Homebrew on macOS with:scoopsconfiguration for Windows package distribution via custom scoop-bucketdraft: falseto enable automatic GitHub release publishing (approval is enforced at the Actions environment level)Documentation (
README.md)Notable Implementation Details
kcc-cacheandkcc-injectorbinaries are distributed through all package managershttps://claude.ai/code/session_01RZdU2QLP9bW65wiHKsaNaT