search

camunda-community-hub / zeebe-kafka-exporter

Export events from Zeebe to Kafka
Apache License 2.0
36 stars 27 forks source link

build: bump version.zeebe from 1.3.6 to 8.1.3 #348

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps version.zeebe from 1.3.6 to 8.1.3. Updates zeebe-bom from 1.3.6 to 8.1.3

Release notes

Sourced from zeebe-bom's releases.

8.1.2

Release 8.1.2

Bug Fixes

Broker

  • Fail to export the process instance modification record to Elasticsearch (#10732)

Merged Pull Requests

  • Add activatedElementInstanceKeys to modification record template (#10733)
  • Distribute deployment in post commit tasks (#10689)

8.1.1

Release 8.1.1

⚠️ Warning

A critical issue was found in the Zeebe ElasticSearch exporter, which leads to records not getting exported after performing a process instance modification. This issue is affecting Zeebe version 8.1.1 only. When updating, it is recommended that you skip version 8.1.1 and update directly to 8.1.2.

Bug Fixes

Broker

  • NPE terminating both multi-instance body and child elements during PI modification (#10537)
  • Using modification, I can't activate an element if an interrupting event subprocess was triggered (#10477)

Misc

  • Ensure RaftStore lock files are created and updated atomically (#10681)
  • RandomizedRaftTest.livenessTestWithNoSnapshot fails because member is ACTIVE not READY (#10545)
  • Failed to take snapshot in leader because index entry is not found (#9761)

Merged Pull Requests

  • Ensure raft storage lock file is update atomically (#10683)
  • fix(raft): do not handle response if role is already closed (#10640)
  • fix: take snapshot if nothing was exported since last snapshot (#10611)
  • Remove interrupted state on event subprocess activation (#10609)
  • test: fix unfinished stubbing of command response writer (#10605)
  • Improve s3 backup store client reliability (#10603)
  • Fix NPE during PI modification (#10601)

8.1.0

Release 8.1.0

:warning: Warning

A critical issue was found on Operate data importer which may lead to incidents not being imported to Operate. This issue is affecting only Operate installations which where updated from 8.0, and not new installations of Operate. When updating, it is recommended that you skip versions 8.1.0 and update directly to 8.1.1.

Enhancements

Broker

  • Writer timer triggered event with process instance key (#9519)
  • Export all records to ES by default (#8338)
  • Feature Request: On Timer events add scheduling at specific time (#3038)
  • I can access the numberOf* multi-instance properties (#2893)

... (truncated)

Commits
  • 1b72df6 [maven-release-plugin] prepare release 8.1.3
  • f0635f7 build(project): update go embedded version data
  • 2cbfdde merge: #10870
  • 233163a test(qa): increase timeout of complete topology
  • 93bb41c refactor(qa): log connecting/disconnecting a node for diagnostics
  • 8e8ef00 merge: #10866
  • b2722ee test(scheduler): add test ensuring other actors can run in between retries
  • 82a27a4 test(scheduler): simplify parameterized tests
  • 619dc6d fix(scheduler): yield thread on retry
  • c67043c test(scheduler): test all strategies where applicable
  • Additional commits viewable in compare view


Updates zeebe-build-tools from 1.3.6 to 8.1.3

Release notes

Sourced from zeebe-build-tools's releases.

8.1.2

Release 8.1.2

Bug Fixes

Broker

  • Fail to export the process instance modification record to Elasticsearch (#10732)

Merged Pull Requests

  • Add activatedElementInstanceKeys to modification record template (#10733)
  • Distribute deployment in post commit tasks (#10689)

8.1.1

Release 8.1.1

⚠️ Warning

A critical issue was found in the Zeebe ElasticSearch exporter, which leads to records not getting exported after performing a process instance modification. This issue is affecting Zeebe version 8.1.1 only. When updating, it is recommended that you skip version 8.1.1 and update directly to 8.1.2.

Bug Fixes

Broker

  • NPE terminating both multi-instance body and child elements during PI modification (#10537)
  • Using modification, I can't activate an element if an interrupting event subprocess was triggered (#10477)

Misc

  • Ensure RaftStore lock files are created and updated atomically (#10681)
  • RandomizedRaftTest.livenessTestWithNoSnapshot fails because member is ACTIVE not READY (#10545)
  • Failed to take snapshot in leader because index entry is not found (#9761)

Merged Pull Requests

  • Ensure raft storage lock file is update atomically (#10683)
  • fix(raft): do not handle response if role is already closed (#10640)
  • fix: take snapshot if nothing was exported since last snapshot (#10611)
  • Remove interrupted state on event subprocess activation (#10609)
  • test: fix unfinished stubbing of command response writer (#10605)
  • Improve s3 backup store client reliability (#10603)
  • Fix NPE during PI modification (#10601)

8.1.0

Release 8.1.0

:warning: Warning

A critical issue was found on Operate data importer which may lead to incidents not being imported to Operate. This issue is affecting only Operate installations which where updated from 8.0, and not new installations of Operate. When updating, it is recommended that you skip versions 8.1.0 and update directly to 8.1.1.

Enhancements

Broker

  • Writer timer triggered event with process instance key (#9519)
  • Export all records to ES by default (#8338)
  • Feature Request: On Timer events add scheduling at specific time (#3038)
  • I can access the numberOf* multi-instance properties (#2893)

... (truncated)

Commits
  • 1b72df6 [maven-release-plugin] prepare release 8.1.3
  • f0635f7 build(project): update go embedded version data
  • 2cbfdde merge: #10870
  • 233163a test(qa): increase timeout of complete topology
  • 93bb41c refactor(qa): log connecting/disconnecting a node for diagnostics
  • 8e8ef00 merge: #10866
  • b2722ee test(scheduler): add test ensuring other actors can run in between retries
  • 82a27a4 test(scheduler): simplify parameterized tests
  • 619dc6d fix(scheduler): yield thread on retry
  • c67043c test(scheduler): test all strategies where applicable
  • 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 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 ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #353.