repo updates

[giorez]

ciao Rafal,
since the main modules (luci-app-modemband and luci-app-modemdata) are quite functional could you pls update the repo with most updated version. Otherwise, to use your modules, I need to istall them manually loosing the chance to just use opkg update/upgrade. Is not a big issue, itìs just convenient. thanks for everything.

[4IceG]

Ciao :)

I will see...
In order to update repository, I cannot modify packages frequently (and that is the situation right now).

[Zerogiven]

@4IceG maybe this workflow can help you: https://github.com/Zerogiven-OpenWRT-Packages/package-feed/blob/main/.github/workflows/update-feed.yml (oh yes and of course you need the scripts https://github.com/Zerogiven-OpenWRT-Packages/package-feed/tree/main/.scripts)

I have created it for my custom repo feed and automated it nearly completely. It catches the release assets and copies them into the correct directories. But for now it is optimized for my repo/releases which has two restrictions:

1. The package has to be named <package_name+version>_<arch>_<openwrt_version>.ipk or for kmods <package_name+version>_<arch>_<target>_<subtarget>_<openwrt_version>.ipk
2. The feed directory structure has to be /<OpenWRT_Version>/packages/<cpu_arch> and /<OpenWRT_Version>/kmods/<target>/<subtarget>

However, i think this can be easily adapted and modified. Then you have a manual workflow where you can just enter the owner/repo path. You also can trigger it inside an github workflow for example if you create a release and want to send it automatically to the repo feed:

    trigger-feed-update:
      needs: create-release
      runs-on: ubuntu-latest
      steps:
        - name: Trigger package feed update
          env:
            GH_TOKEN: ${{ secrets.FEED_DISPATCH_TOKEN }}
          run: |
            gh api repos/YOUR_USERNAME/package-feed/dispatches \
              -f event_type=webhook-release \
              -f 'client_payload[repository]=${{ github.repository }}' \
              -f 'client_payload[tag]=${{ github.ref_name }}'

I also have some reusable workflows for building packages and creating a release if you are interested: https://github.com/Zerogiven/gh-openwrt-package-build-workflows

Example:

name: Build OpenWRT package (release)

on:
  push:
    tags:
      - "v*"

jobs:
  build-packages:
    strategy:
      matrix:
        include:
          # 24.10
          - openwrt_version: '24.10'
            openwrt_build_version: '24.10.4'
            arch: 'x86_64'
          - openwrt_version: '24.10'
            openwrt_build_version: '24.10.4'
            arch: 'aarch64_cortex-a53'
          - openwrt_version: '24.10'
            openwrt_build_version: '24.10.4'
            arch: 'aarch64_cortex-a72'
          - openwrt_version: '24.10'
            openwrt_build_version: '24.10.4'
            arch: 'arm_cortex-a7'
          - openwrt_version: '24.10'
            openwrt_build_version: '24.10.4'
            arch: 'arm_cortex-a7_neon-vfpv4'
          - openwrt_version: '24.10'
            openwrt_build_version: '24.10.4'
            arch: 'arm_cortex-a9'

          # 23.05
          - openwrt_version: '23.05'
            openwrt_build_version: '23.05.6'
            arch: 'x86_64'
          - openwrt_version: '23.05'
            openwrt_build_version: '23.05.6'
            arch: 'aarch64_cortex-a53'
          - openwrt_version: '23.05'
            openwrt_build_version: '23.05.6'
            arch: 'aarch64_cortex-a72'
          - openwrt_version: '23.05'
            openwrt_build_version: '23.05.6'
            arch: 'arm_cortex-a7'
          - openwrt_version: '23.05'
            openwrt_build_version: '23.05.6'
            arch: 'arm_cortex-a7_neon-vfpv4'
          - openwrt_version: '23.05'
            openwrt_build_version: '23.05.6'
            arch: 'arm_cortex-a9'
      fail-fast: false

    uses: Zerogiven/gh-openwrt-package-build-workflows/.github/workflows/reusable-build.yml@main
    with:
      package_name: 'reaction'
      sdk_packages: 'reaction'
      artifacts_patterns: 'reaction*.ipk'
      openwrt_version: ${{ matrix.openwrt_version }}
      openwrt_build_version: ${{ matrix.openwrt_build_version }}
      arch: ${{ matrix.arch }}
      free_disk_space: true
      verbose: false

  create-release:
    needs: build-packages
    permissions:
      contents: write
    uses: Zerogiven/gh-openwrt-package-build-workflows/.github/workflows/reusable-release.yml@main
    with:
      artifact_pattern: 'reaction-*'
      release_file_pattern: '*.ipk'
      tag_name: ${{ github.ref_name }}
    secrets:
      RELEASE_TOKEN: ${{ secrets.OWRT_PACKAGE_RELEASE_TOKEN }}

(Example Release: https://github.com/Zerogiven-OpenWRT-Packages/reaction/releases/tag/v2.2.1%2Bbuild.5)

Also be aware that the reusable workflows are not tagged to a version for now, it uses the main branch. This will be changed soon tagged to v1.

For me this helps a lot to keep the feed repo up to date with latest packages. Oh yes and it also handles "_all" packages which gets copied into /<OpenWRT_Version>/all/ directory.

I try to improve them a bit but i also not want to overcomplicate it - feel free to response with ideas/impressions 🙂