Releases: camunda-community-hub/pyzeebe
Releases · camunda-community-hub/pyzeebe
v3.0.0rc2
v3.0.0rc1
Merge pull request #172 from camunda-community-hub/feature/async-worker Feature/async
v2.3.1
v2.3.0
Changes
- Official support for zeebe 0.26.0.0
- Start watcher thread that reactivates stopped threads #112.
- Add boolean parameter called
watch
toZeebeWorker.work
to start the watcher thread. This will by default be disabled.
- Add boolean parameter called
- Give up on connection to zeebe gateway after configured amount #75.
- Add parameter to
ZeebeWorker
andZeebeClient
constructor calledmax_connection_retries
.
- Add parameter to
Enhancements
- Use pytest fixtures to simplify tests.
v2.2.3
Changes
Deprecations
- Remove python 3.5 support
Dependencies
-
Package dependencies:
- zeebe-grpc: 0.24.3.3 -> 0.25.1.0
- Removed grpcio and protobuf from dependencies as they're included in zeebe-grpc
-
Development dependencies:
- pytest: 6.1.1 -> 6.2.1
- sphinx: 3.2.1 -> 3.4.2
- sphinx-rtd-theme: 0.5.0 -> 0.5.1
- coveralls: 2.1.2 -> 2.2.0
- importlib-metadata: 2.0.0 -> 3.3.0
- coverage: 5.3 -> 5.3.1
v2.2.2
Changes
- Using a named logger. This means
pyzeebe
logging levels can now be set using:logging.getLogger("pyzeebe").setLevel(logging.WARNING)
v2.2.1
Changes
- Using
zeebe-grpc
package - Updated dependencies:
grpcio
from 1.31.0 to 1.32.0
- Updated development dependencies:
coverage
from 5.2.1 to 5.3pytest
from 6.0.1 to 6.1.1mypy
from 0.782 to 0.790importlib-metadata
from 1.7.0 to 2.0.0
v2.2.0
v2.1.0
Added:
- Full task api to
@worker.task
decorator:variables_to_fetch
param - which variables to fetch from the workflow instance scopetimeout
param - how long until zeebe gives up on jobmax_jobs_to_activate
param - max jobs the worker can perform simultaneously (per task)
- Automatic
variables_to_fetch
. (fromfunction.__code__.co_varnames
) - Base exception class named:
PyZeebeException
from which all custom exceptions inherit
Fixed:
v2.0.1
Fixed:
TaskDecorator
andZeebeTaskRouter
not being in exports