Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump zeebe.version from 8.2.3 to 8.2.9 #298

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 25, 2023

Bumps zeebe.version from 8.2.3 to 8.2.9.
Updates io.camunda:zeebe-bom from 8.2.3 to 8.2.9

Release notes

Sourced from io.camunda:zeebe-bom's releases.

8.2.8

Release 8.2.8

Bug Fixes

Broker

  • Regression in deploying large payloads (#13233)
  • No space left on device while receiving snapshot leads to unhealthy followers (#6232)

Misc

  • When the deployment of a process definition failed, clients can still start new process instances of the actually non-existing process definition (#13254)
  • Segfault on enabling async scheduled task (#13164)
  • On processing error lastProcessPosition is not updated which can cause inconsistent state on restart (#13101)
  • Failing jobs with job push enabled breaks the job lifecycle (#12933)
  • ModifyProcessInstanceRejectionTest#shouldRejectActivationWhenAncestorScopeIsNotFlowScope test fails on Windows (#12875)
  • StackOverflowError when terminating process with a lot of child processes (#8955)

Maintenance

  • Avoid usage of actor in gateway job stream (#13037)

Merged Pull Requests

  • [Backport stable/8.2] deps(parent): bump zeebe-test-container to 3.6.0 (#13265)
  • Reset the diskSpaceAvailable flag correctly (#13260)
  • Prevent StackOverFlowError during termination of children (#13258)
  • Mark command as processed even on processing error (#13206)
  • fix(scheduler): ensure callbacks added after future is completed are executed (#13139)
  • Fix line separators ModifyProcessInstanceRejectionTest (#13117)
  • test(qa): fix flakiness by awaiting snapshot on restarted broker (#13112)
  • test: simplify GCS restore acceptance tests (#13050)
  • Allow ActorFuture.onComplete to be called by non-actors (#13043)
  • refactor(engine): migrate job processors to typed record processor (#12943)
  • Refactor job command preconditions (#12753)

8.2.7

Bug Fixes

Misc

  • Straight-through processing loop may cause problems (#12957)

Maintenance

  • Use Snyk to check for license issues or dependency vulnerabilities (#9245)

Merged Pull Requests

  • Detect and reject call activities calling itself in a straight-through loop (#13056)
  • test(broker): wait until records are exported before taking snapshot (#13039)
  • Detect and reject straight-through processing loops (#13025)
  • Integrate Snyk into CI (#12922)
  • Allow deploying benchmarks on stable VMs (#12815)

8.2.6

Bug Fixes

Broker

  • Failing to write to logstream during stepdown is logged as error (#12780)

Misc

  • Catch all error events by using empty 'errorCode' does not work (#12837)
  • Cannot resolve output mapping incident on a none end event (#12833)
  • Journal reset resulting in an intermediate state which is detected as corruption (#12754)
  • 8.2.3 Degradation: Creating an oversized BPMN causes unrecoverable failure (#12591)

... (truncated)

Commits
  • 8066d80 [maven-release-plugin] prepare release 8.2.9
  • 557a622 build(project): update go embedded version data
  • b83d94f Merge branch 'stable/8.2' into release-8.2.9
  • 750f5f7 merge: #13627
  • 885646b fix(release): increased maven & Go release timeout
  • 85e42a9 Revert "build(project): update go embedded version data"
  • 627c9a6 Revert "[maven-release-plugin] prepare release 8.2.9"
  • ff0a262 Revert "[maven-release-plugin] prepare for next development iteration"
  • 87dda96 [maven-release-plugin] prepare for next development iteration
  • f066dc3 [maven-release-plugin] prepare release 8.2.9
  • Additional commits viewable in compare view

Updates io.camunda:zeebe-parent from 8.2.3 to 8.2.9

Release notes

Sourced from io.camunda:zeebe-parent's releases.

8.2.8

Release 8.2.8

Bug Fixes

Broker

  • Regression in deploying large payloads (#13233)
  • No space left on device while receiving snapshot leads to unhealthy followers (#6232)

Misc

  • When the deployment of a process definition failed, clients can still start new process instances of the actually non-existing process definition (#13254)
  • Segfault on enabling async scheduled task (#13164)
  • On processing error lastProcessPosition is not updated which can cause inconsistent state on restart (#13101)
  • Failing jobs with job push enabled breaks the job lifecycle (#12933)
  • ModifyProcessInstanceRejectionTest#shouldRejectActivationWhenAncestorScopeIsNotFlowScope test fails on Windows (#12875)
  • StackOverflowError when terminating process with a lot of child processes (#8955)

Maintenance

  • Avoid usage of actor in gateway job stream (#13037)

Merged Pull Requests

  • [Backport stable/8.2] deps(parent): bump zeebe-test-container to 3.6.0 (#13265)
  • Reset the diskSpaceAvailable flag correctly (#13260)
  • Prevent StackOverFlowError during termination of children (#13258)
  • Mark command as processed even on processing error (#13206)
  • fix(scheduler): ensure callbacks added after future is completed are executed (#13139)
  • Fix line separators ModifyProcessInstanceRejectionTest (#13117)
  • test(qa): fix flakiness by awaiting snapshot on restarted broker (#13112)
  • test: simplify GCS restore acceptance tests (#13050)
  • Allow ActorFuture.onComplete to be called by non-actors (#13043)
  • refactor(engine): migrate job processors to typed record processor (#12943)
  • Refactor job command preconditions (#12753)

8.2.7

Bug Fixes

Misc

  • Straight-through processing loop may cause problems (#12957)

Maintenance

  • Use Snyk to check for license issues or dependency vulnerabilities (#9245)

Merged Pull Requests

  • Detect and reject call activities calling itself in a straight-through loop (#13056)
  • test(broker): wait until records are exported before taking snapshot (#13039)
  • Detect and reject straight-through processing loops (#13025)
  • Integrate Snyk into CI (#12922)
  • Allow deploying benchmarks on stable VMs (#12815)

8.2.6

Bug Fixes

Broker

  • Failing to write to logstream during stepdown is logged as error (#12780)

Misc

  • Catch all error events by using empty 'errorCode' does not work (#12837)
  • Cannot resolve output mapping incident on a none end event (#12833)
  • Journal reset resulting in an intermediate state which is detected as corruption (#12754)
  • 8.2.3 Degradation: Creating an oversized BPMN causes unrecoverable failure (#12591)

... (truncated)

Commits
  • 8066d80 [maven-release-plugin] prepare release 8.2.9
  • 557a622 build(project): update go embedded version data
  • b83d94f Merge branch 'stable/8.2' into release-8.2.9
  • 750f5f7 merge: #13627
  • 885646b fix(release): increased maven & Go release timeout
  • 85e42a9 Revert "build(project): update go embedded version data"
  • 627c9a6 Revert "[maven-release-plugin] prepare release 8.2.9"
  • ff0a262 Revert "[maven-release-plugin] prepare for next development iteration"
  • 87dda96 [maven-release-plugin] prepare for next development iteration
  • f066dc3 [maven-release-plugin] prepare release 8.2.9
  • 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)

Bumps `zeebe.version` from 8.2.3 to 8.2.9.

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

Updates `io.camunda:zeebe-parent` from 8.2.3 to 8.2.9
- [Release notes](https://github.com/camunda/zeebe/releases)
- [Commits](camunda/camunda@8.2.3...8.2.9)

---
updated-dependencies:
- dependency-name: io.camunda:zeebe-bom
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.camunda:zeebe-parent
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested review from saig0 and Zelldon as code owners July 25, 2023 21:15
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 25, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 27, 2023

Superseded by #299.

@dependabot dependabot bot closed this Jul 27, 2023
@dependabot dependabot bot deleted the dependabot/maven/zeebe.version-8.2.9 branch July 27, 2023 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants