Set up WASI CI and releases

[battila7]

Brief

As we're now able to build CryptID.native into WASI, we should automate this process.

Task

Setup an Azure Pipeline which

• compiles CryptID.native into a WASI-compatible WASM module
• upon release, creates a new GitHub release with this artifact.

[battila7]

Depends on #68

[syrusakbary]

I'd love to see a way to automatically upload the module to WAPM, if possible.

Let me know if that might interest you and I can help on the process :)

[battila7]

@syrusakbary Thanks for dropping by! Prior to creating this issue, I considered wapm as another target for our releases, however, I was concerned a bit. I might be mistaken, but for me it seems like that wapm is mostly for executables, and not libraries.

If that's not the case, then we will happily setup a wapm release pipeline for sure!

[syrusakbary]

@battila7 Thanks for the feedback! WAPM is also a great fit for libraries.

I will talk with the team to see what we can do to make it clearer on the website :)

Note: A lot of features for the library use case are coming soon... stay tuned!

[battila7]

@syrusakbary Great, thanks! I'm really looking forward to those features as a fan of WASM!

If we need any help regarding the wapm deployment, we will reach out to you!