0.4.17

Features

• Add remote state middleware to experimental package (here). This middleware circumvents Inngest's step output limits by storing the data in an arbitrary place, like a self-hosted S3 bucket.

Fixes

• Fix invoke app_id default and data type.
• Fix not encrypting invoke data. This must be opted in because it's a breaking change (using the encrypt_invoke_data arg).

When opting into encrypted invoke data, a zero downtime release process is:

1. Update Python SDK to at least 0.4.17.
2. Deploy app.
3. Set encrypt_invoke_data=True.
4. Deploy app.

What's Changed

• Add experimental remote state middleware by @amh4r in https://github.com/inngest/inngest-py/pull/178
• Fix test failures by @amh4r in https://github.com/inngest/inngest-py/pull/181
• Remove black and isort by @amh4r in https://github.com/inngest/inngest-py/pull/182
• Fix invoke: app ID default and data type by @amh4r in https://github.com/inngest/inngest-py/pull/186
• Fix step.invoke data is not encrypted by @amh4r in https://github.com/inngest/inngest-py/pull/187
• Add encrypt_invoke_data arg to encryption middleware by @amh4r in https://github.com/inngest/inngest-py/pull/188
• Bump version to 0.4.17 by @amh4r in https://github.com/inngest/inngest-py/pull/183

Full Changelog: https://github.com/inngest/inngest-py/compare/0.4.16...0.4.17