WAPM publishing

[jcaesar]

Implements #29.

I've tested this on some other repository, but I obviously can't test it on yours. So there might be some quirks.

For the login token, you'll have to:

• Log in to wapm.io,
• click your user account icon (top right),
• Settings,
• Access Tokens,
• Create new Token.

And then register that as a new repository secret on this github repo.

[jcaesar]

Actually, can I ask you to wait with merging this for a bit? It might be necessary to downgrade rust to 1.56 for the release build because of this bug.

[ikanago]

OK, please notify me after the bug is fixed.

[ikanago]

After the bug is fixed, I will test these workflows.

[ikanago]

These files are identical among jobs, so just checking on one job, ubuntu-20.04 for example, is enough.

[jcaesar]

That is what I thought at first, too, but tell me: Won't the publish step for the other os still run, creating a release with some missing files?

omekasy/.github/workflows/release.yml

Lines 89 to 95 in a36cd66

	- name: Publish
	if: ${{ contains(github.ref, '/tags/') }}
	uses: softprops/action-gh-release@v1
	with:
	files: ${{ env.PKG_PATH }}
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

[jcaesar]

I give up. Instead of that bug above getting fixed, webassembly.sh is getting more and more broken. You could of course publish to wapm.io for other reasons, but I'm not quite sure what those would be.

(Unrelated: I might package this for nixpkgs, though. [Edit:] Easy.)