Releases: inngest/inngest-py
Releases · inngest/inngest-py
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:
- Update Python SDK to at least
0.4.17
. - Deploy app.
- Set
encrypt_invoke_data=True
. - Deploy app.
What's Changed
- Add experimental remote state middleware by @amh4r in #178
- Fix test failures by @amh4r in #181
- Remove black and isort by @amh4r in #182
- Fix invoke: app ID default and data type by @amh4r in #186
- Fix step.invoke data is not encrypted by @amh4r in #187
- Add encrypt_invoke_data arg to encryption middleware by @amh4r in #188
- Bump version to 0.4.17 by @amh4r in #183
Full Changelog: 0.4.16...0.4.17
v0.4.16
v0.4.15
v0.4.14
v0.4.13
Features
- Add experimental in-band sync feature. You can opt in by setting the env var
INNGEST_ALLOW_IN_BAND_SYNC=1
.
Fixes
- Fix configured serve path (e.g.
INNGEST_SERVE_PATH
env var) not considered when creating Inngest route handlers. - Fix ugly exception when event sending fails.
Improvements
- Print URL when an outgoing request fails.
Full changelog
v0.4.12
v0.4.11
v0.4.10
v0.4.9
0.4.8
Experimental changes
- Update
inngest.experimental.encryption_middleware
to support cross-language encryption. Now the Python SDK can send encrypted events to the TypeScript SDK, and vice-versa. While this is a breaking change, it doesn't require a major version bump since the middleware is still experimental