bytecodealliance / actions Goto Github PK

Just used these actions for the first time and they're awesome, thanks for working on them!

I also was looking to install wit-bindgen in addition to wasmtime and wasm-tools for my use case so I wanted to open a feature request for supporting that as well. Not urgent at all and it's more niche than the other two, but figured others may find it interesting!

GitHub Actions workflows that use v1 break, and need: bytecodealliance/actions/wasmtime/[email protected]

I got this log pulling this action into a project recently for installing wasm-tools. The wasm-tools release process changed in bytecodealliance/wasm-tools#1416 which I suspect may need to be reflected here?

I know the wasi-sdk project is not a part of the bytecodealliance organization but it seems useful (to me, at least) to have an easy-to-use GitHub action for installing it in CI workflows. This seems as good a place as any for storing such an action. What do you all think?

Why? This lets you get listed on the GitHub Actions marketplace: https://github.com/marketplace?category=&type=actions&verification=&query=wasmtime https://github.com/marketplace?category=&type=actions&verification=&query=wasm-tools

I would like to transfer these two repositories into the @bytecodealliance organization to make them "official": https://github.com/jcbhmr/setup-wasm-tools https://github.com/jcbhmr/setup-wasmtime . I'm not sure how to do that or if @bytecodealliance is open to that. 🤷‍♀️

In https://github.com/bytecodealliance/wit-bindgen/actions/runs/7980244336/job/21789477528?pr=851 I'm seeing the rate limiting that can happen when the token isn't specified. I thought though I've seen actions historically which don't require specifying the token but they instead inherit it (somehow, I'm not sure). Is it perhaps an environment variable that could be configured automatically if no other explicit input is provided?