Releasing

The Git tag is always the full package version: <pkgver>-<pkgrel>. Pushing it triggers release.yml, which refuses to run if the tag does not match PKGBUILD.

Packaging-only patch

Changed keygen.js, PKGBUILD, .desktop, … but not IDA itself.

1. Bump pkgrel in PKGBUILD (2 → 3).
2. Commit.
3. Tag and push:

   git tag 9.4.260714-3
   git push origin main --tags
   

Same .run is rebuilt and re-patched; pacman -Syu moves users to -3.

New IDA build

1. Upload the new .run to the generic registry:

   curl --user "<user>:<PKG_TOKEN>" \
     --upload-file ida-pro_XX_x64linux.run \
     "https://git.xyz.bzh/api/packages/software/generic/ida-installer/<newver>/ida-pro_XX_x64linux.run"
   

2. In PKGBUILD: set pkgver=<newver>, update the first entry of sha256sums (the .run), set pkgrel=1. Update _installer if the filename changed.
3. Commit.
4. Tag and push:

   git tag <newver>-1
   git push origin main --tags
   

sha256sums order: [0] = the .run, [1] = ida-pro.desktop.

Commit messages

Conventional Commits, enforced only softly (unconventional commits are filtered out of the changelog by cliff.toml). Groups: feat, fix, perf, refactor, docs, build, ci, test, chore. Use scopes, e.g. fix(pkgbuild): ....

If a release job fails

• Tag mismatch — fix pkgver/pkgrel, delete the tag locally and remotely, re-tag.
• Installer 404 — the .run was not uploaded to the generic registry under that exact pkgver.
• keygen.js could not patch — the byte pattern changed in this IDA build; keygen.js needs updating for the new version.