Report preparation
What happened?
Now let me also check the closed issues and search specifically for any release/CI/assets related issues:Good — no results found for that search. I've reviewed all 12 open issues and none of them relate to missing release assets or executables. I also checked for any closed issues via search with no matches. This is a new, distinct bug report. Here's the GitHub issue ready to file:
Bug Report: Release v0.7.18.6 Missing Four Executables in Assets
Title: [BUG] Release v0.7.18.6 assets incomplete — only 4 of expected 8 files present
## What
The GitHub Release page for **v0.7.18.6** lists only **4 assets** under the
Assets section, but a clean build should produce **8 downloadable files**.
The missing four executables/archives are not attached and cannot be downloaded
by users.
## Why
Users on Linux (and potentially other platforms) rely on the pre-built release
assets to install or evaluate AetherSDR without building from source. When half
the expected binaries are absent from a release, users:
- Cannot install the version at all if the asset for their platform/format is
among the missing four
- May download an incomplete or wrong-platform build without realizing it
- Are blocked from testing or using the latest features advertised in the
release notes
This also affects the Windows Inno Setup installer path introduced in earlier
releases — if `AetherSDR-Setup.exe` is one of the missing assets, Windows
users are completely unable to install v0.7.18.6.
## How Other Clients Handle It
SmartSDR (Windows-only, closed source) uses an internal FlexRadio distribution
channel, so this comparison doesn't apply. Other open-source SDR projects that
use GitHub Releases for CI artifacts — such as **SDR++** and **CubicSDR** —
typically attach the full asset matrix (Linux AppImage, Windows installer,
Windows portable ZIP, macOS DMG, debug symbols, checksums) in a single
automated CI/CD step. When a CI job fails mid-run, partial asset sets like
this one can result.
## Suggested Behavior
1. **Verify the expected asset list** for a complete release. Based on prior
releases and the existence of the Inno Setup Windows installer (added in the
build system), a full v0.7.18.6 release should include assets along the
lines of:
AetherSDR--linux-x86_64.AppImage ← Linux portable
AetherSDR--linux-x86_64.tar.gz ← Linux tarball
AetherSDR--Setup.exe ← Windows Inno Setup installer
AetherSDR--windows-x86_64.zip ← Windows portable ZIP
AetherSDR--debug-symbols.tar.gz ← (optional) debug symbols
SHA256SUMS ← checksum manifest
Source code (zip) ← auto-generated by GitHub
Source code (tar.gz) ← auto-generated by GitHub
*(Exact names and count may differ — the point is the CI job should define
and enforce the complete expected set.)*
2. **Re-run the release CI workflow** for v0.7.18.6 (or delete and re-publish
the release) so all platform targets complete and upload successfully.
3. **Add a CI gate** that fails the release workflow if the number of uploaded
assets is less than the expected count — preventing partial releases from
being published silently in the future. Example in a GitHub Actions workflow:
```yaml
- name: Verify asset count
run: |
COUNT=$(gh release view ${{ github.ref_name }} --json assets \
--jq '.assets | length')
EXPECTED=8
if [ "$COUNT" -lt "$EXPECTED" ]; then
echo "ERROR: Only $COUNT of $EXPECTED expected assets uploaded."
exit 1
fi
- Consider adding a SHA256SUMS or checksums.txt asset to each release
so users can verify integrity after download.
Protocol Hints
N/A — this is a CI/release pipeline issue, not a FlexLib/SmartSDR protocol
issue.
Steps to Reproduce
- Navigate to https://github.com/ten9876/AetherSDR/releases/tag/v0.7.18.6
- Expand the Assets section
- Observe only 4 items listed (excluding auto-generated source archives)
- Compare against the asset count of a prior complete release
Environment
- Affected release: v0.7.18.6
- Observed: 4 assets
- Expected: 8 assets (per a clean build)
---
No duplicate was found among the open issues — none of the 12 open issues (or anything in the closed/search results) touches CI, release assets, missing executables, or the build pipeline. This is safe to file as a new bug report.
A couple of notes before you submit:
- **Verify the exact expected asset names** against a prior complete release (e.g., v0.7.18.5 or earlier) so you can list the four specific missing filenames in the issue body — that makes it much easier for the maintainer to identify which CI job failed.
- The `[BUG]` label and `priority: high` would be appropriate here since it blocks installation for some users.
### What did you expect?
_No response_
### Steps to reproduce
_No response_
### Radio model & firmware
_No response_
### Linux distro & Qt version
_No response_
Report preparation
What happened?
Now let me also check the closed issues and search specifically for any release/CI/assets related issues:Good — no results found for that search. I've reviewed all 12 open issues and none of them relate to missing release assets or executables. I also checked for any closed issues via search with no matches. This is a new, distinct bug report. Here's the GitHub issue ready to file:
Bug Report: Release v0.7.18.6 Missing Four Executables in Assets
Title:
[BUG] Release v0.7.18.6 assets incomplete — only 4 of expected 8 files presentAetherSDR--linux-x86_64.AppImage ← Linux portable
AetherSDR--linux-x86_64.tar.gz ← Linux tarball
AetherSDR--Setup.exe ← Windows Inno Setup installer
AetherSDR--windows-x86_64.zip ← Windows portable ZIP
AetherSDR--debug-symbols.tar.gz ← (optional) debug symbols
SHA256SUMS ← checksum manifest
Source code (zip) ← auto-generated by GitHub
Source code (tar.gz) ← auto-generated by GitHub
so users can verify integrity after download.
Protocol Hints
N/A — this is a CI/release pipeline issue, not a FlexLib/SmartSDR protocol
issue.
Steps to Reproduce
Environment