Testing: Resources/organization

[bhelx]

• Where do we store the test .wasm files how do we keep them versioned? Probably makes sense to keep them in one repo then use git submodules but we also discussed maybe building some infrastructure around this
• Ensure that the extism-runtime.wasm kernel is updated automatically, or semi-automatically (4 hours)
  • SDKs that require the kernel should get automatic PRs when this file changes

[bhelx]

I part 1 was taken care of with the extism/plugins repo

@zshipko is part 2 take care of by the development build process?

[zshipko]

The only thing left is to update the go-sdk and js-sdk when the kernel changes. I think this could be considered complete and we can open some issues on those repos for more specific tasks.

[neuronicnobody]

Can continue manual approach for now while determining how to automate more fully

[chrisdickinson]

Noting that I'll take this on as a back-burner task. Goals are:

• Make sure the Go and JS SDKs continue to work against extism-runtime.wasm changes
• Keep the extism-runtime.wasm file vendored in the Go and JS SDKs up-to-date automatically. (Possibly by submitting PRs against those repos whenever the runtime artifact changes.)

[nilslice]

@chrisdickinson this may be a viable option... https://github.com/orgs/community/discussions/49745

Imagine running a step like this (opening a PR with the new kernel to go-sdk and js-sdk) from the release action in extism/extism