Release v0.0.4

feat(aiproxy): api-key header (#32)

Handle error from OpenAI without locking the conversation
Support Api-Key header that Azure OpenAI use ( use SPIN_VARIABLE_OPENAI_API_KEY_METHOD environment variable to decide which method to use for passing the api key )
Allow refunding all tokens if there is no usage
Lock emscripten version. After emscripten 3.1.74 the standard libraries are built with non-mvp features. The NEAR wasm spec is at mvp, and so the build was broken.
Enhance test suites to support the different Api-Key passing methods

Release v0.0.3

FT metadata, web4, docs (#30)

Expose the ft_metadata method to the contract wasm. It is needed by wallets to properly show the balance.
Docs about setting up the Fungible Token contract
Implementation of web4_get to be able to serve a web page from the contract
Scripts for bundling for web4, using the AI proxy frontend as an example
Docs about submitting javascript code to the contract
Docs for deploying the AI proxy to Spin cloud

Release v0.0.2

• added Fungible Token contract

v0.0.1

Add a release with a zip file of example contract wasm builds:

• nft.wasm ( the NFT contract from examples/nft )
• minimum_web4.wasm ( the minimum web4 contract from examples/minimumweb4 )

These contracts can then be downloaded from the release and deployed to any account. Updates to the javascript code can then be done using function access keys calling the post_javascript function.