Prepare new release v0.17.

Author: ignatz

.dockerignore

@@ -8,11 +8,15 @@ traildepot/
 
 client
 !client/rust
+!client/testfixture/guests/rust
 deploy/
 docs/
 !docs/examples/record_api_rs
 examples/
 !examples/custom-binary
+!examples/wasm-guest-rust
+!examples/coffee-vector-search/guests/rust
+!examples/collab-clicker-ssr/guests/rust
 
 Dockerfile*
 .docker*

CHANGELOG.md

@@ -1,6 +1,13 @@
+## v0.17.0
+
+* Add new WASM runtime based on [wasmtime](https://github.com/bytecodealliance/wasmtime). More information in a dedicated update [article](https://trailbase.io/blog/switching_to_a_wasm_runtime).
+  * This is a transitional release containing both the V8 and WASM runtime. The plan is to eventually remove V8.
+  * We expect WASM to unlock a lot of opportunities going forward, from increased performance (though JS is slower), strict state isolation, flexible guets language choice, more extensibility... check the [article](https://trailbase.io/blog/switching_to_a_wasm_runtime).
+* Update JavaScript and Rust dependencies.
+
 ## v0.16.9
 
-* Add support for non-transactional bulk edits to experimental "transacation record API" and expose it in the JS/TS client. Thanks so much @ibilux 🙏.
+* Add support for non-transactional bulk edits to experimental "transaction record API" and expose it in the JS/TS client. Thanks so much @ibilux 🙏.
 * Update Rust dependencies.
 
 ## v0.16.8

docs/src/content/blog/switching_to_a_wasm_runtime.mdx

@@ -119,14 +119,14 @@ were unreliable in our previous V8 integration.
 
 ### Less Code
 
-As mentioned before, switching off V8 removes a lot of high-scrunity code, cuts
+As mentioned before, switching off V8 removes a lot of high-scrutiny code, cuts
 binary size roughly in half and lets us build truly static binaries with MUSL.
 
 ### Rethinking Composition & Licensing Model
 
 The increased flexibility and performance provided by the new WASM runtime
 opens up a path to making this a singular entry-point for extending TrailBase
-(including SQLite extensions) as opposed to framework use-caess.
+(including SQLite extensions) as opposed to framework use-cases.
 In turn, this may allow us to adopt a more popular copyleft license w/o
 inflicting obligations on your business-logic.
 
@@ -159,7 +159,7 @@ optimize.
 
 The first difference you'll encounter is the need for a build-step: JS/TS -> WASM[^5].
 For now, we recommend to copy the template in `examples/wasm-guest-ts` or
-`examples/wasm-guest-ts`, dependning on whether you prefer TypeScript or
+`examples/wasm-guest-ts`, depending on whether you prefer TypeScript or
 JavaScript respectively.
 You can then simply run `pnpm install && pnpm build` to build the WASM component.
 For TrailBase to pick up you `*.wasm` component, they need to be placed in
@@ -245,8 +245,8 @@ to improve the documentation.
 
 ## Next-Steps
 
-First and foremost, we'd love to hear from you, make the transition as smooth
-as possible and the WASM runtime best-in-class 🙏.
+First and foremost, we'd love to hear from you. We'd like to make the
+transition as smooth as possible and the WASM runtime best-in-class 🙏.
 
 Once the new runtime integration has seen more mileage and unforeseen surprises
 are worked out, we'd like to sunset V8 expediently.