Skip to content
This repository has been archived by the owner on Jan 30, 2022. It is now read-only.

chore(deps): bump version.zeebe from 0.24.1 to 0.25.0 #43

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps version.zeebe from 0.24.1 to 0.25.0.
Updates zeebe-bom from 0.24.1 to 0.25.0

Release notes

Sourced from zeebe-bom's releases.

Zeebe 0.25.0

Release: 0.25.0

Enhancements

Broker

  • Add an experimental configuration flag to disable explicit flushing in Raft (#5570)
  • A gateway should know a partition health. (#5481)
  • Admin api to trigger snapshot in a broker (#5405)
  • Detect issues when upgrading the broker to a new version (#5381)
  • Expose RocksDB column family options as configuration (#5279)
  • Support now for date / time / date and time constructors (#5140)
  • Make Raft's serialization format backwards compatible (#5038)
  • As an User I can get the message key as response from the message publish command (#4794)
  • Add broker steps startup/shutdown metrics (#3913)

Java Client

  • Allow using JobWorker in a try-with-resources (#4837)
  • As an User I can get the message key as response from the message publish command (#4794)
  • Java client should send the client type and version with his auth request (#4265)

Go Client

  • Support preventing duplicate deployment of workflow by introducing a digest value (#5144)
  • As an User I can get the message key as response from the message publish command (#4794)
  • Go client should send the client type and version with his auth request (#4264)

Bug Fixes

Broker

  • Re-processing detects inconsistency due to Deployment distribution (#5568)
  • A stepdown might result in inconsistent log in the old leader (#5360)
  • Raft elects two leaders at the same term (#5356)
  • Broker is not recovering from out of disk space (#5329)
  • Documentation shows different backpressure algorithm name (#5257)
  • Reject deployments with null output mapping (#5253)
  • Reject Deployments with invalid timer cycles (#5248)
  • Reject deployments with empty error event, or ignore empty error events (#5247)
  • Workers broken as gRPC connections fail (quickly after registering workers) in versions >23.1 in some configurations (#5187)
  • Kryo prints a lot of class loading failures (#5146)
  • Restart takes too long or never completes when snapshot contains many files (#5135)
  • A broker tries to communicate to a restarted broker using it's old IP (#5116)
  • Will not compact after exporters are removed (#5105)
  • Broker does not stops processing if it is already out of disk space on start (#5093)
  • Fail to access an element of a List with FEEL expression (#5086)
  • Segmentation fault when closing the broker (#5066)
  • Record with Non-ASCII characters fails to export to Elasticsearch (#5059)
  • Default settings ignored when using SPRING_CONFIG_LOCATION (#4976)
  • Rolling update not possible with 0.24 (#4961)
  • Event Scope State is not cleaned up when the message start event subscription is closed (#4959)
  • Variable state is not cleaned up if an event is triggered (#4957)
  • Elastic exporter get broken pipe with big records (#4951)
  • Health of follower partitions is sometimes reported as unhealthy (#4943)
  • Message Start Event of an Event Subprocess is not setting variables and not allowing Output mapping (#4884)
  • Benchmark 0.24.0-RC1 stopped making progress (#4871)
  • Segfault in RocksDB via metrics exporter (#4868)
  • Parallel multi-instance call activity cannot collect output (#4860)
Commits

Updates zeebe-build-tools from 0.24.1 to 0.25.0

Release notes

Sourced from zeebe-build-tools's releases.

Zeebe 0.25.0

Release: 0.25.0

Enhancements

Broker

  • Add an experimental configuration flag to disable explicit flushing in Raft (#5570)
  • A gateway should know a partition health. (#5481)
  • Admin api to trigger snapshot in a broker (#5405)
  • Detect issues when upgrading the broker to a new version (#5381)
  • Expose RocksDB column family options as configuration (#5279)
  • Support now for date / time / date and time constructors (#5140)
  • Make Raft's serialization format backwards compatible (#5038)
  • As an User I can get the message key as response from the message publish command (#4794)
  • Add broker steps startup/shutdown metrics (#3913)

Java Client

  • Allow using JobWorker in a try-with-resources (#4837)
  • As an User I can get the message key as response from the message publish command (#4794)
  • Java client should send the client type and version with his auth request (#4265)

Go Client

  • Support preventing duplicate deployment of workflow by introducing a digest value (#5144)
  • As an User I can get the message key as response from the message publish command (#4794)
  • Go client should send the client type and version with his auth request (#4264)

Bug Fixes

Broker

  • Re-processing detects inconsistency due to Deployment distribution (#5568)
  • A stepdown might result in inconsistent log in the old leader (#5360)
  • Raft elects two leaders at the same term (#5356)
  • Broker is not recovering from out of disk space (#5329)
  • Documentation shows different backpressure algorithm name (#5257)
  • Reject deployments with null output mapping (#5253)
  • Reject Deployments with invalid timer cycles (#5248)
  • Reject deployments with empty error event, or ignore empty error events (#5247)
  • Workers broken as gRPC connections fail (quickly after registering workers) in versions >23.1 in some configurations (#5187)
  • Kryo prints a lot of class loading failures (#5146)
  • Restart takes too long or never completes when snapshot contains many files (#5135)
  • A broker tries to communicate to a restarted broker using it's old IP (#5116)
  • Will not compact after exporters are removed (#5105)
  • Broker does not stops processing if it is already out of disk space on start (#5093)
  • Fail to access an element of a List with FEEL expression (#5086)
  • Segmentation fault when closing the broker (#5066)
  • Record with Non-ASCII characters fails to export to Elasticsearch (#5059)
  • Default settings ignored when using SPRING_CONFIG_LOCATION (#4976)
  • Rolling update not possible with 0.24 (#4961)
  • Event Scope State is not cleaned up when the message start event subscription is closed (#4959)
  • Variable state is not cleaned up if an event is triggered (#4957)
  • Elastic exporter get broken pipe with big records (#4951)
  • Health of follower partitions is sometimes reported as unhealthy (#4943)
  • Message Start Event of an Event Subprocess is not setting variables and not allowing Output mapping (#4884)
  • Benchmark 0.24.0-RC1 stopped making progress (#4871)
  • Segfault in RocksDB via metrics exporter (#4868)
  • Parallel multi-instance call activity cannot collect output (#4860)
Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because not all of the dependencies being updated are post 1.0.0.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

  • Update frequency
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps `version.zeebe` from 0.24.1 to 0.25.0.

Updates `zeebe-bom` from 0.24.1 to 0.25.0
- [Release notes](https://github.com/zeebe-io/zeebe/releases)
- [Commits](camunda/camunda@0.24.1...0.25.0)

Updates `zeebe-build-tools` from 0.24.1 to 0.25.0
- [Release notes](https://github.com/zeebe-io/zeebe/releases)
- [Commits](camunda/camunda@0.24.1...0.25.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Oct 22, 2020
@dependabot-preview
Copy link
Contributor Author

Superseded by #46.

@dependabot-preview dependabot-preview bot deleted the dependabot/maven/version.zeebe-0.25.0 branch November 6, 2020 17:44
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants