Releases: tetratelabs/proxy-wasm-go-sdk
Release v0.23.0
It's been a while since the last release like almost one year. There hasn't been notable change though, we are releasing the new version v0.23.0. The only one notable change is the introduction of properties
package that facilitates the access to the "property" values.
Note that the tag 0.22.0
was mistakenly created before but not assigned as "release", so this new release skips 0.22.0 hence published with 0.23.0 tag.
Enjoy!
Full Changelog: v0.21.0...main
proxy-wasm-go-sdk v0.21.0
proxy-wasm-go-sdk v0.21.0 is a maintenance release with a few improvements and some version bumps.
ProxyTest improvements
proxytest
now includesProxyGetProperty
andProxySetProperty
thanks to @jmjolysc for contributing the change (#250)- further improves were contributed from @dgryski (#353) thanks!
Other Notable Changes
- Improves the
http_headers
examples/http_headers thanks @jonathanvila - Upgrades Wazero to the latest version (1.0.0-pre.8)
- CI is now also testing against Envoy 1.25, Istio 1.16 and building via TinyGo 0.26
Contributors: @omidtavakoli @mathetake @jmjolysc @codefromthecrypt @jonathanvila @nacx @while1malloc0 @dgryski @evacchi
Full Changelog: v0.20.0...v0.21.0
in-Wasm end-to-end framework
Thanks to the contribution by @anuraaga, now Proxy-Wasm Go SDK has support for directly testing your Proxy-Wasm binary in the Wasm virtual machine powered by wazero.io. More precisely, the proxytest
package can be used to run either your plugins on your native machine or the compiled Wasm binary inside a Wasm virtual machine. Regardless of choice, the same emulation test code can be used. See this example for the demonstration.
Enjoy!
Contributors: @mathetake @anuraaga @codefromthecrypt
Code changes: v0.19.0...v0.20.0
proxytest: case-intensive headers and trailers
Now the proxytest framework becomes case-intensive on headers and trailers just like Envoy implementations.
Thank you @jlourenc for the contribution!
TinyGo 0.23.0 support
Fixes an edge case bug in dispatched callbacks
This contains a bug fix for an edge-case with HTTP dispatches:
If a plugin sends a local reply in dispatched callbacks and the connection
has been terminated, then wasm VM crashes and eventually, envoy fails
to recover and envoy process exits with an uncaught exception.
See #270 for detail.
v0.16.0
v0.15.0
Fix nil panic around OnTick
Introduction of VMContext, and PluginContext
This tag is intentionally cut as v0.13.0 which seems odd considering that the previous one is cut with v0.3.0. The point is that we mistakenly cut v0.12.0 a few months ago, and we've already delete it, but it is still referenced as a "latest" by pkg.go.dev (https://pkg.go.dev/github.com/tetratelabs/proxy-wasm-go-sdk). That's why we cut 0.13.0 for now as a workaround. In anyway, the tag is just a tag so we hope this wouldn't be a problem:) Enjoy!