Releases: inngest/inngest-py
Releases · inngest/inngest-py
v0.4.2
v0.4.1
Fixes
- Fix internal validation error since
ctx.stack.stack
in the request body can be null
v0.4.0
This release contains some breaking changes. Please see our docs for a detailed migration guide.
New features
- Improved existing middleware hooks and added new hooks. These changes support more robust middleware, like Sentry.
- Added the priority function configuration.
Breaking changes
- Changed some middleware function signatures.
- Removed
async_mode
arg ininngest.django.serve
. This is now inferred based on whether any of your Inngest functions areasync
. - Removed
NonRetriableError.cause
.
v0.3.16
New features
- Add
timeout
option tostep.invoke
andstep.invoke_by_id
.
v0.3.15
New features
- Add
RetryAfterError
, which can be used to schedule a retry at a specific time.
Fixes
- Fix validation error when an Inngest Server sets
event.data
tonull
instead of{}
.
v0.3.14
Improvements
- Auto-detect async mode for Django. Its
async_mode
serve
kwarg will be removed in version v0.4. - Raise an error if using async functions and a Django version below 5.
- Stop logging a warning when falling back to the synchronous HTTP client.
v0.3.13
New features
- Add DigitalOcean Functions support.
v0.3.12
New features
- Add support for
step.run
callback args (e.g.step.run("my-step", my_callback, arg_1, arg_2)
). - Change experimental encryption middleware (
inngest.experimental.EncryptionMiddleware
) to use NaCL.
Fixes
- Fix returning secure introspection when in dev mode. This isn't a security fix since the secure introspection response doesn't include secrets and the changes only affect local development.
v0.3.11
New features
- Experimental encryption middleware (
inngest.experimental.EncryptionMiddleware
)
v0.3.10
Fixes
- Use a connection pool when sending HTTP requests.