I wonder why this workflow doesn't have a write permission and yet softprops/action-gh-release can make a release. Are we using a PAT ? If yes, we should use automatic token authentication instead.

This is so cool! Thanks for putting it together.

Do you have any suggestions on how to merge/test this? Is there some way to manually trigger he binary release for the latest release, or should I try it only on the next release (and then I suppose it will magically work as this workflow is triggered when I push a new tag)?

It appears like the latest deno >=2.1.0 broke something.

denoland/deno#27172

Need to wait until it's resolved or pin the deno version to 2.0.6