feat(ci): build binaries for develop branch

[martylukyy]

This PR adds a condition to the existing Run GoReleaser build and publish tags step
to also build binaries for the develop branch and not just for tags.

Summary by CodeRabbit

• Chores
  • Updated release workflow to build snapshot releases from the develop branch in addition to tag-based releases.
  • Improved release process reliability by enforcing strict artifact validation, ensuring all expected files are present before publishing.

[coderabbitai]

Walkthrough

The release workflow is extended to support both snapshot and full builds. The goreleaserbuild step now triggers on develop branch pushes in addition to tag pushes, with conditional arguments that run full releases with cleanup for tags and snapshot-only builds for develop. The Upload assets step is tightened to error when expected artifacts are missing.

Changes

Release Workflow Enhancements

Layer / File(s)	Summary
Conditional GoReleaser builds for tags and snapshots .github/workflows/release.yml	GoReleaser step runs on both tag refs and the develop branch, with conditional args: release --clean for tags and snapshot build skipping publish/sign for develop.
Artifact upload validation .github/workflows/release.yml	Upload assets step is configured with if-no-files-found: error to fail the workflow when expected dist files are missing.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A rabbit's wish for smoother releases fast,
With snapshots on develop and tags to last,
And errors when artifacts go astray,
The workflow now catches them without delay!
✨ hops with joy

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: enabling binary builds for the develop branch in the CI workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/build-develop-binaries

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/release.yml (1)

175-184: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Gate "Upload assets" on tags/develop, or it will fail on main pushes.

The job condition (Line 113) runs goreleaserbuild on every non-PR push, including main. On a main push, the GoReleaser step is skipped (Line 164 matches only tags or develop), so no dist/* artifacts are produced. Since this step has no if: and now uses if-no-files-found: error, the workflow will fail on main pushes (previously this was just a warning).

Add the same condition used by the GoReleaser step:

🐛 Proposed fix

       - name: Upload assets
+        if: startsWith(github.ref, 'refs/tags/') || github.ref == 'refs/heads/develop'
         uses: actions/upload-artifact@v7
         with:
           name: qui
           path: |
             dist/*.tar.gz
             dist/*.zip
             dist/*.deb
             dist/*.rpm
           if-no-files-found: error

🤖 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 around lines 175 - 184, The "Upload assets"
step (uses: actions/upload-artifact@v7, name: Upload assets) will fail on main
pushes because it always runs and now has if-no-files-found: error; update that
step to include the same conditional used by the GoReleaser step (the
goreleaserbuild job/step) so it only runs for tags and the develop branch (i.e.,
add the identical if: expression used by the goreleaserbuild step to the Upload
assets step), or alternatively change if-no-files-found to ignore if you prefer
non-failing behavior.

🤖 Prompt for all review comments with 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.

Outside diff comments:
In @.github/workflows/release.yml:
- Around line 175-184: The "Upload assets" step (uses:
actions/upload-artifact@v7, name: Upload assets) will fail on main pushes
because it always runs and now has if-no-files-found: error; update that step to
include the same conditional used by the GoReleaser step (the goreleaserbuild
job/step) so it only runs for tags and the develop branch (i.e., add the
identical if: expression used by the goreleaserbuild step to the Upload assets
step), or alternatively change if-no-files-found to ignore if you prefer
non-failing behavior.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 57ea7109-18c2-47f9-8321-8c72f16563da

📥 Commits

Reviewing files that changed from the base of the PR and between 11ace50 and f9adb5e.

📒 Files selected for processing (1)

• .github/workflows/release.yml