Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ jobs:
run: npm ci --ignore-scripts

- name: Run GoReleaser
run: goreleaser release --clean
run: goreleaser release --clean --snapshot

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== release workflow ==\n'
wc -l .github/workflows/release.yml
sed -n '1,180p' .github/workflows/release.yml

printf '\n== ci workflow ==\n'
wc -l .github/workflows/ci.yml
sed -n '1,220p' .github/workflows/ci.yml

Repository: mindfiredigital/DeepScanBot

Length of output: 7238


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== goreleaser references ==\n'
rg -n --hidden --glob '.github/workflows/*.yml' 'goreleaser|snapshot|release --clean' .github/workflows

printf '\n== release workflow around the release step ==\n'
nl -ba .github/workflows/release.yml | sed -n '70,100p'

Repository: mindfiredigital/DeepScanBot

Length of output: 812


🌐 Web query:

GoReleaser snapshot mode release --snapshot does not publish artifacts documentation

💡 Result:

GoReleaser's snapshot mode (triggered by the --snapshot flag) is specifically designed for local builds or CI validation and does not publish artifacts [1]. By design, when you run GoReleaser with --snapshot, it skips the publishing step and only generates artifacts locally within the dist directory [1][2]. This behavior is intentional; the tool maintains a strict separation between snapshot builds (for validation) and full release builds (which include publishing) [1][3]. If you require the ability to publish builds that are not full releases, GoReleaser offers alternative solutions: 1. Nightly Builds (GoReleaser Pro): For use cases requiring automated publishing of development builds (such as pushing Docker images or binaries on every commit), GoReleaser Pro provides a --nightly flag designed to handle these scenarios [3][4][5]. 2. Manual Workflows: Because snapshot mode skips publishing, some users implement manual CI steps (e.g., custom shell scripts or secondary GitHub Actions) to manually upload or push artifacts generated in the dist folder to their desired destinations (such as S3 buckets or Docker registries) [5]. For more information on the intended use of snapshots, you can refer to the official GoReleaser documentation [1].

Citations:


Remove --snapshot from the release job. Snapshot mode is fine in .github/workflows/ci.yml for validation, but here it only writes to dist/ and skips publishing, so the GitHub release can go out without binaries/checksums. Use goreleaser release --clean in this workflow.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/release.yml at line 84, Update the release workflow’s
GoReleaser invocation to remove the --snapshot flag, leaving goreleaser release
--clean so the release job publishes binaries and checksums.

Source: Coding guidelines

env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Expand Down
4 changes: 0 additions & 4 deletions .golangci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,6 @@ run:
timeout: 5m
tests: true

output:
formats:
- format: colored-line-number

linters:
enable:
- bodyclose
Expand Down