Release: 1.1.0-alpha1
Enhancements
Broker
- Detect segment descriptor field corruption (#7041)
Go Client
- Split address and port in zbctl (#3104)
Bug Fixes
Broker
- Segment descriptor is loaded twice (#7116)
- MaxAppendBatchSize configuration printed out at broker startup up shows incorrect value (#7048)
- Back to back role changes cause ZeebePartition to go unhealthy and transition to inactive (#6997)
- The advertised address should be unresolved locally in the broker (#6983)
- Broker crashes if there is an empty log segment (#6979)
- The event scope of a timer start event is not removed when already triggered (#6976)
- A call activity can't be completed or terminated (#6959)
- The temporary variables are not removed on termination (#6958)
- The event scope of a timer start event is not removed (#6955)
- I can't resolve an incident caused by the input collection for a sequential multi-instance (#6952)
- Partition incorrectly marked as unhealthy when broker is closing. (#6938)
- Multi-instance variables are wrong after resolving an incident (#6933)
- Variables are overridden when the subprocess is completed (#6926)
- Memory leak in NettyMessagingService (#6878)
- Unable to resolve incident for multi instance output element expression failure (#6546)
- Redeploying process model with Timer start event causes retriggering (#6515)
- The source record position may point to a wrong record (#5420)
- ElasticExporter export metrics for bulk even when bulk is not flushed successfully (#4830)
Go Client
- [zbctl] unable to publish message containing space in message name (#6596)
- Diff in zbctl test output is incorrect (#6967)
Misc
- Zeebe-broker-1 and zeebe-broker-2 will remind "warn" every five minutes io.camunda.zeebe.snapshots.impl.FileBasedTransientSnapshot - Failed to delete pending snapshot" (#7098)
- NPE in StandaloneGateway (#7018)
- IOException: No space left on device (#6505)
Documentation
- Some env variables are mentioned wrong in configuration template (#6325)
Merged Pull Requests
- Adds new issues to the Zeebe project in "Awaiting triage" status (#7125)