[Feature Request]: Improve information for GitHub releases

[fdcastel]

Which feature would you like to have?

Problem

1. The assets property of GitHub releases is currently empty for releases such as this example.

   To obtain a download link, users must navigate to the Armbian website manually. For example: link.

   I understand there are numerous builds available (e.g., bananapicm4io, rpi4b, etc.). But it would be ideal for all relevant builds to be included within the assets property, preferably tagged for easier identification.

2. Also, there is currently no metadata to distinguish between stable and trunk releases.

   The prerelease property is not being appropriately utilized to mark trunk releases.
   The current workaround involves filtering out releases with the "trunk" string in their name property, but this is suboptimal.

Why?

I wish to write a script to automate the download of the latest stable release. Something in the lines of:

# powershell

# Get latest release information
$ProgressPreference = 'SilentlyContinue'
$latestRelease = (Invoke-WebRequest 'https://api.github.com/repos/armbian/build/releases' -UseBasicParsing | ConvertFrom-Json) |
    Where-Object -Property 'name' -notlike '*trunk*' | 
        Select-Object -First 1

$assetsUrl = $latestRelease.assets_url
$assets = Invoke-WebRequest $assetsUrl -UseBasicParsing | ConvertFrom-Json

Funding

• I am willing to cover expenses

[github-actions]

Hey @fdcastel !

Looks like it's your first time interacting with Armbian here on GitHub.

Welcome and thank you for taking the time to report an issue ❤️.

Don't forget to star ⭐ the repo.

[github-actions]

Jira ticket: AR-2567

[igorpecovnik]

The assets property of GitHub releases is currently empty for releases such as

Primary problem is that images releases are not directly attached to the build framework versioning (https://github.com/armbian/build/). We generate images daily (or point stable) in separate repository https://github.com/armbian/os which has assets in their releases https://github.com/armbian/os/releases Stable releases are only on our infra for many reasons - first is the obvious - file size limit and second is download speed. Which is bad compared to our CDN. Which should, in theory, provide top download speed from anywhere in the world. Especially when you use torrent download options, which downloads from all mirrors at once.

Armbian build framework releases could produce build framework Debian package but this also won't help much as Framework interacts with Git and uses cloud caches. Git clone of this repo should be enough.

I understand your concerns, but this is build framework that make generic version-less OS. We have development of build framework and there is OS version combined with upstream version (jammy / bookworm / ...). Point releases are different in version and fixed sources. How to represent this better, I am open for suggestions.