run result: https://github.com/cxzhong/Singular/actions/runs/22613451855

Thanks! This is very close to the make_tar.sh recipe and should solve the “official tarball vs GitHub tarball” issue. It would be great if you could address the following:

1. The header comment says “creating (or editing) a release”, but the trigger is only release: published. Please either adjust the wording or add the respective event types.

2. For attaching assets to a GitHub release, please request explicit token permissions, so this works also under more restrictive defaults. Like in the job that uploads the asset:

jobs:
  release-tarball:
    permissions:
      contents: write

3. In the tarball step, please enable “fail on pipeline errors” and add simple existence checks before copying/packing the artefacts, so that failures are immediate and easy to diagnose.

run result https://github.com/cxzhong/Singular/actions/runs/22625882592

@jankoboehm Can you review this again? It only runs by manunal or release a new version

Thanks a lot, we are looking into it, please hang on.