.github/workflows/release.yml (2)

8-10: Consider if packages: write permission is needed.

The packages: write permission is typically required for pushing to GitHub Container Registry. Since the GoReleaser config doesn't include Docker/container publishing, this permission may be unnecessary. Removing unused permissions follows the principle of least privilege.

♻️ Optional: Remove if not needed

 permissions:
   contents: write
-  packages: write

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/release.yml around lines 8 - 10, Review the workflow
permissions block and remove the unnecessary elevated permission by deleting or
commenting out the "packages: write" entry under the permissions map (the
"permissions:" block that currently lists "contents: write" and "packages:
write") if your GoReleaser configuration does not publish Docker or push to
GitHub Package/Container Registry; retain "contents: write" if required and
ensure no other steps rely on "packages: write" before removing it.

---

24-25: Consider enabling Go module caching.

Disabling cache (cache: false) will cause every release build to re-download dependencies, slowing down the workflow. Unless there's a specific caching issue being worked around, enabling the cache improves build times.

♻️ Optional: Enable caching

       - name: Set up Go
         uses: actions/setup-go@v5
         with:
           go-version: '1.22'
-          cache: false

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/release.yml around lines 24 - 25, The workflow currently
sets cache: false for the Go setup (see the go-version and cache keys);
re-enable module caching by changing the cache setting to true or to the
appropriate module cache mode (e.g., enable Go modules caching) so dependencies
are cached between runs—update the cache key in the release.yml step that
configures go-version to enable caching rather than false.

.goreleaser.yaml (1)

71-74: Add explicit branch field to repository blocks to prevent default-branch migration issues.

Both brews and scoops repository configurations lack explicit branch fields. GoReleaser uses the repository's default branch if omitted, which can break publishing if the tap's default branch changes (e.g., from master to main). Add branch: main under each repository block:

Example fix

brews:
  - name: gitstart
    repository:
      owner: shinokada
      name: homebrew-gitstart
      branch: main
      token: "{{ .Env.HOMEBREW_TAP_TOKEN }}"

scoops:
  - repository:
      owner: shinokada
      name: scoop-bucket
      branch: main
      token: "{{ .Env.SCOOP_BUCKET_TOKEN }}"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.goreleaser.yaml around lines 71 - 74, The repository blocks in the brews
and scoops sections omit an explicit branch, causing GoReleaser to use the repo
default branch which can break when defaults change; update each repository
block (the brews entry for name: gitstart and the scoops repository entry) to
add branch: main alongside owner, name, and token so the tap publish targets the
intended branch explicitly.