Thanks for the changes.

However, read the specs again linked via #3241 (comment)

There must be a space followed by a space for text mode or * for binary mode between hash and filename. The sha265sum and md5sum defaults to text mode, so there are two spaces. You are adding a tab instead for some reason.

https://www.gnu.org/software/coreutils/manual/html_node/md5sum-invocation.html

https://www.gnu.org/software/coreutils/manual/html_node/sha2-utilities#sha2-utilities

termux/upload-release-action@5f5653d

I don't know what mode node crypto internally uses compared with gnu utils, which would have to be checked too. Apparently, in text mode, \r\n may get translated to \n.

https://unix.stackexchange.com/questions/127959/md5sum-command-binary-and-text-mode/127961#127961

https://stackoverflow.com/questions/17988090/what-are-the-differences-between-md5-binary-mode-and-text-mode

https://stackoverflow.com/questions/70360822/python-binary-mode-vs-encoding-and-its-sha256

Hopefully for following, specially with globs, there are duplicate file name checks since different (sub)directories could have files with same basenames.

termux/upload-release-action@422a9a2

Also, follow commit guidelines.

https://github.com/termux/termux-app#For-Maintainers-and-Contributors

Also, despite the fixes to upload-release-action for other termux repos, I still haven't decided if adding an external action dependency without any advantages should be done, specially something written in frickin' node/javascript ;)

Maybe other termux devs can give their opinion. Technically, termux-packages uses it for packages and bootstrap, so any effects would get translated.