v0.54.6

What's Changed

• Disambiguate error message for denied invocation by @brooksmtownsend in #391
• Changed workflow to run builds on our supported os'es by @brooksmtownsend in #392
• Updated release image to bullseye by @brooksmtownsend in #394
• fixed release env in host core by @brooksmtownsend in #396

Full Changelog: v0.54.5...v0.54.6

v0.54.4

What's Changed

• chore(chart): Bump chart version to latest host release by @thomastaylor312 in #382
• Updates the host to support actors written in TinyGo by @autodidaddict in #383
• allow host container to gracefully shut down in response to SIGTERM by @connorsmith256 in #384

Full Changelog: v0.54.3...v0.54.4

wasmcloud-host-0.5.1

A Helm chart for running wasmCloud hosts on Kubernetes

v0.54.3

What's Changed

• fix(host_core): Makes chunking work in all places by @thomastaylor312 in #380
• chore(*): Bumps version for patch release by @thomastaylor312 in #381

Full Changelog: v0.54.2...v0.54.3

v0.54.2

What's Changed

• chore(chart): Bumps various versions in chart by @thomastaylor312 in #375
• Replaced webpack with esbuild by @brooksmtownsend in #350
• [BUG] Dashboard values cannot handle base64 '=' padding characters by @emattiza in #377
• Terminate gracefully during SIGTERM by @autodidaddict in #379

Full Changelog: v0.54.1...v0.54.2

v0.54.1

chore(*): Bumps app version in preparation for patch release (#374)

I also fixed some clippy lints that had popped up in the NIF

Signed-off-by: Taylor Thomas <[email protected]>

v0.54.0

bump versions for 0.54.0 (#372)

Signed-off-by: Brooks Townsend <[email protected]>

wasmcloud-host-0.5.0

A Helm chart for running wasmCloud hosts on Kubernetes

wasmcloud-host-0.4.0

A Helm chart for running wasmCloud hosts on Kubernetes

v0.53.0

Added

• NATS message "bubble wrap" that prevents host processes from exiting when there's a temporary loss of NATS connectivity in #363
• Invocation chunking support, any invocation that exceeds the NATS max size limit will be automatically chunked and delivered with actors and providers running at least wasmbus-rpc 0.8.3 #354

Changed

• Identified and fixed a memory spike with starting capability providers, each capability provider will now require only ~10Mb free memory to start rather than ~500Mb in #347
• Capability providers that exit, gracefully or due to panic, will now be properly cleaned up and removed from the host inventory in #360
• Actors that exit, gracefully or due to panic, because of a Wasmex issue will now safely exit #366
• RPC failures that are caused by a timeout will now indicate the cause of the issue in the host log in #362