v0.3.0

Breaking changes

Lua API level is now roto.api_version = 2. Update setup scripts:

• roto.lambda.function_ is now roto.lambda.fn
• roto.request is now roto.wire
• roto.intercept_request is now roto.hooks.request
• roto.mqtt.on_connect / on_subscribe are now roto.hooks.mqtt_connect / mqtt_subscribe
• roto.s3.link_dir returns {bucket, prefix, count} instead of a bare count

New features

• roto.call supports kms and logs
• roto.json_decode(text) is available in setup scripts, for parsing roto.wire responses
• Service modules get roto.array(table) and roto.null, matching setup scripts

v0.2.2

Optional Lua service bundle for Roto.

v0.2.1

Optional Lua service bundle for Roto.

v0.2.0

New features

• roto.s3.link(bucket, key, file, opts?) and roto.s3.link_dir(bucket, prefix, dir, opts?) register host files as S3 objects without copying them; reads are served from the file and roto never writes, moves or deletes it
• --enable-lua-api serves POST /roto-api/lua to run setup-API Lua scripts against a running server (loopback only, rejects browser requests, returns result, print output and errors with line numbers)

v0.1.1

Fixes

• Inspection object downloads now always use application/octet-stream. Header stripping was case-sensitive, so a stored Content-Type could leak through.
• Lambda command executor no longer fails when a command exits before reading stdin (broken-pipe race).
• CI: clippy lints and moved smoke-test script paths.

v0.1.0

What's Changed

• Add minimal IoT MQTT WebSocket listener and Lua policy hooks by @vivainio in #2

New Contributors

• @vivainio made their first contribution in #2

Full Changelog: v0.0.2...v0.1.0