chore(deps): bump version.zeebe from 0.24.1 to 0.25.1

[dependabot-preview]

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

Release notes

Sourced from zeebe-bom's releases.

Zeebe 0.25.1

Release: 0.25.1

Enhancements

Broker

• Control inconsistency detection with an experimental feature flag (#5759)

Merged Pull Requests

• [BACKPORT 0.25] Add experimental flag to control inconsistency detection (#5765)

Zeebe 0.25.0

Release: 0.25.0

NOTE: Since 0.24.4, there is a new experimental feature in Zeebe which checks for inconsistencies when replaying the log - that is, when the workflow engine is restarting, it will attempt to verify that it rebuilt the in-memory state correctly. This was primarily built to assert that upgrades were successful or not. Zeebe 0.25.1 introduces a feature flag which controls whether or not this feature is enabled. As we've found a few bugs in there, we recommend you upgrade to 0.25.1 as soon as possible, which will allow you to turn on this feature only during upgrades; once you've verified that the upgrade was successful, you can then restart your nodes without the flag. In the meantime we will keep on polishing this feature such that it can be used at all times.

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)

Commits

• 147304c [maven-release-plugin] prepare release 0.25.1
• ff5907f chore(project): update go embedded version data
• 7cc99d4 Merge #5765
• 89af464 chore(broker): add test for feature flag
• 325c0c9 test(engine): turn off inconsistency detection test
• 2a629db chore(broker): introduce new experimental flag to turn of reprocessing detection
• 5f8a494 chore(project): prepare for next release
• d1a54d6 chore(ci): update compat data
• 4711988 fix(ci): push changes to branch
• a1752af [maven-release-plugin] prepare for next development iteration
• Additional commits viewable in compare view

Updates zeebe-build-tools from 0.24.1 to 0.25.1

Release notes

Sourced from zeebe-build-tools's releases.

Zeebe 0.25.1

Release: 0.25.1

Enhancements

Broker

• Control inconsistency detection with an experimental feature flag (#5759)

Merged Pull Requests

• [BACKPORT 0.25] Add experimental flag to control inconsistency detection (#5765)

Zeebe 0.25.0

Release: 0.25.0

NOTE: Since 0.24.4, there is a new experimental feature in Zeebe which checks for inconsistencies when replaying the log - that is, when the workflow engine is restarting, it will attempt to verify that it rebuilt the in-memory state correctly. This was primarily built to assert that upgrades were successful or not. Zeebe 0.25.1 introduces a feature flag which controls whether or not this feature is enabled. As we've found a few bugs in there, we recommend you upgrade to 0.25.1 as soon as possible, which will allow you to turn on this feature only during upgrades; once you've verified that the upgrade was successful, you can then restart your nodes without the flag. In the meantime we will keep on polishing this feature such that it can be used at all times.

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)

Commits

• 147304c [maven-release-plugin] prepare release 0.25.1
• ff5907f chore(project): update go embedded version data
• 7cc99d4 Merge #5765
• 89af464 chore(broker): add test for feature flag
• 325c0c9 test(engine): turn off inconsistency detection test
• 2a629db chore(broker): introduce new experimental flag to turn of reprocessing detection
• 5f8a494 chore(project): prepare for next release
• d1a54d6 chore(ci): update compat data
• 4711988 fix(ci): push changes to branch
• a1752af [maven-release-plugin] prepare for next development iteration
• Additional commits viewable in compare view

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)

[dependabot-preview]

This pull request will no longer be automatically closed when a new version is found as this pull request was created by Dependabot Preview and this repo is using a version: 2 config file. You can close this pull request and let Dependabot re-create it the next time it checks for updates.