Announcing Spin 2.3.1
Melissa Klein
spin
webassembly
wasi
component model
release
wasmtime
Today, we are happy to announce Spin 2.3.1, which comes closely on the heels of last week’s version 2.3. These versions include the following upgrades to Spin:
- Improve support for multiple trigger types in a Spin Application
- Improve support for working with OCI
- Upgraded PHP template to support PHP 8.2
In this release, we also squashed some bugs to bring you a better experience while developing your Spin Applications!
Improved Support for Multiple Trigger Types in a Spin Application
In Spin 2.2, one of our community members contributed a pull request for multiple triggers in a single Spin application. This feature is still in early development but support for it has expanded in Spin 2.3.1. It is exciting to see this frequently requested feature move towards full support. We will continue to work on this feature and once it is stabilized we will add documentation and examples to the Developer website.
In the Spin 2.3.1 release, the spin add command will now allow you to add different trigger types to an existing application. This makes trying out this experimental feature so much easier! In addition, the spin up command can interrogate triggers about which flags they support. If run spin up with a flag that applies to one trigger but not others, spin up can now figure out which trigger cares about the flag.
Again, this is an experimental feature and work is in progress to make it feature complete. Also, any plugin triggers that you may use will need to be updated to support multiple triggers. In the meantime, please try it out and let us know if you run into any issues. You can open an issue on GitHub or reach out on our Discord server.
Improved Support for OCI
In this release we have made changes to improve the way you work with OCI images. First, spin registry login will now work with Azure Container Registries giving you more options to store and retrieve artifacts. In addition, spin registry push now ensures that applications pushed to OCI have unique image config fields for unique Spin application content and metadata. This ensures that content is replaced with newer versions.
Bug fixes include:
- Fix for Azure Container Registry login flow for
spin registry push
- Fix for a bug where the spin registry push generated the same OCI config object for every application pushed, resulting in the same “image ID” associated by
containerd to every Spin application.
Thank You!
We would like to thank the over 75 contributors to the Spin project and all of those in our growing community. Every comment, issue, and pull request helps us to make Spin better!
A special mention goes out to the maintainers of the Bytecode Alliance projects, particularly the Wasmtime project and the developers working on WASI and the WebAssembly component model. Their work is instrumental in supporting Spin.
Stay In Touch
If you are interested in Spin, Fermyon Cloud, or other Fermyon projects, join the chat in the Fermyon Discord server and follow us on X (formally Twitter) @fermyontech and @spinframework!
If you want to get involved in the Spin project, join us at our Spin Community Developers Meeting on the fourth Monday of every month at 11 a.m. Eastern US Time (4 p.m. Berlin Time). Our next one is on March 25. You can watch recordings of the previous meetings on our YouTube Channel.