Hopefully this will be the last fix to have the CI all green.
It seems the GitHub action termux/upload-release-action requires, in its latest version, to provide a checksum value to work. This will generate (and upload) a file named CHECKSUMS-sha256.txt with a checksum for all artifacts.
I also found an issue with the uploaded artifacts (using actions/upload-artifact@v4). If the source package is a file with the tar.xz extension, it will be uploaded with the generated package. This is not wanted so I added an extra restriction to fix it. It will prevent this as seen in the release (https://github.com/vitasdk/packages/releases):
Hopefully this will be the last fix to have the CI all green.
It seems the GitHub action termux/upload-release-action requires, in its latest version, to provide a checksum value to work. This will generate (and upload) a file named
CHECKSUMS-sha256.txt
with a checksum for all artifacts.I also found an issue with the uploaded artifacts (using actions/upload-artifact@v4). If the source package is a file with the tar.xz extension, it will be uploaded with the generated package. This is not wanted so I added an extra restriction to fix it. It will prevent this as seen in the release (https://github.com/vitasdk/packages/releases):
Tested on my fork, the release can be seen here https://github.com/scribam/packages/releases/tag/master and the last action here https://github.com/scribam/packages/actions/runs/10161076933
Sorry for the inconvenience related to my different changes