No releases/download tags since 2017

[anphsw]

The project has been stable and working reliably, but the last official release was in 2017, making it difficult for package maintainers to create proper distribution packages that rely on versioned releases rather than git commits.
Please consider creating a new release from the current package state.
Maybe release package versioning may change to YYYYMMDD?
This would greatly help with dependency tracking, reproducible builds, and inclusion in various Linux distributions' repositories.

[braice]

Hello

I understand, I had my release script in the past but it is broken.

I can do a tag by hand on github, do you suggest a specific hash I should tag ?

Best

Brice

[Saentist]

@braice

.github/workflows/auto_release.yml

name: Auto Release

on:
  push:
    branches:
      - master

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v3

      - name: Get current date
        id: date
        run: echo "date=$(date +'%Y%m%d')" >> $GITHUB_OUTPUT

      - name: Get latest tag
        id: tag
        run: |
          latest_tag=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
          echo "latest_tag=$latest_tag" >> $GITHUB_OUTPUT

      - name: Calculate next version
        id: next
        run: |
          latest="${{ steps.tag.outputs.latest_tag }}"
          if [[ $latest =~ v([0-9]+)\.([0-9]+)\.([0-9]+) ]]; then
            major=${BASH_REMATCH[1]}
            minor=${BASH_REMATCH[2]}
            patch=$((BASH_REMATCH[3]+1))
            next_version="v${major}.${minor}.${patch}"
          else
            next_version="v0.0.1"
          fi
          echo "next_version=$next_version" >> $GITHUB_OUTPUT

      - name: Create tag
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          tag="${{ steps.next.outputs.next_version }}-${{ steps.date.outputs.date }}"
          git config user.email "github-actions[bot]@users.noreply.github.com"
          git config user.name "github-actions[bot]"
          git tag "$tag"
          git push origin "$tag"

      - name: Create GitHub Release
        uses: softprops/action-gh-release@v1
        with:
          tag_name: ${{ steps.next.outputs.next_version }}-${{ steps.date.outputs.date }}
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

can be modified if needed

Needed steps

On the main page of repository.
Click the gear icon next to “About”.
Add at least one valid topic, for example: DVB, Streamer, or IPTV.

[anphsw]

@braice
Latest project state should work OK for release, and then for example, every 6-12 month (if project has commits and code auto-builds successfully).

[braice]

Will do ! :-)

[braice]

Just did a release, please tell me if it worked for you

[anphsw]

Builds good (ubuntu 24.04, alpine 3.24), but some issues here:

• reporting version does not contain commit hash or date:

./mumudvb -d
MuMuDVB Version 2.1.0
 --- Build information ---

• release tarball missing 'configure' (it seems like it was not build by github autorelease system)

libtoolize --force
aclocal && autoheader
automake --force-missing --add-missing
autoreconf -i -f

This should be done on server side for release tarballs.

Also, please look at my latest PR which makes command line options compatible with different distributions aimed to select working dirs and pid file from command line for init scripts, but also it enables override for any future config options without change in command line parsing code.
So such options is not needed anymore and can be replaced by "-о card" and "-o server_id":

--card
	The DVB card to use (overrided by the configuration file)

--server_id
	The server id (for autoconfiguration, overrided by the configuration file)