Skip to content

Conversation

ericgregory
Copy link
Contributor

Related to wasmCloud/wasmcloud.com#947, this PR updates compatibility warnings on component examples to reflect the current state of wasm-tools compatibility for each:

  • http-client is fine with latest wasm-tools ✅
  • http-password-checker is fine with latest wasm-tools ✅
  • http-server is fine with latest wasm-tools ✅
  • wasitel-http is fine with latest wasm-tools ✅
  • http-keyvalue-crud requires wasm-tools v1.225.0 ❌
  • invoke component requires wasm-tools v1.225.0 ❌
  • sqldb-postgres requires wasm-tools v1.225.0 ❌

This PR removes the admonitions from the examples that work with the latest wasm-tools, but adds a note in the troubleshooting section at the bottom. It also adds a minimal readme for wasitel-http in order to include the troubleshooting note.

While we're updating, this PR also applies the best practice of excluding generated bindings from Git repos consistently across the examples, removing the ones that were present and updating gitignores accordingly.

Signed-off-by: Eric Gregory <eric@cosmonic.com>
Signed-off-by: Eric Gregory <eric@cosmonic.com>
@ericgregory ericgregory requested a review from a team as a code owner July 16, 2025 13:33
@thomastaylor312
Copy link
Contributor

Sorry @ericgregory this slipped through the cracks. If you can get the tests passing, this should be good to go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants