build(deps): bump github.com/camunda/zeebe/clients/go/v8 from 8.4.5 to 8.5.1 in /go-chaos

[dependabot[bot]]

Bumps github.com/camunda/zeebe/clients/go/v8 from 8.4.5 to 8.5.1.

Release notes

Sourced from github.com/camunda/zeebe/clients/go/v8's releases.

8.5.1

Release 8.5.1

Bug Fixes

Go Client

• zbctl 8.4.0 can't send requests with authorization information (#16015)

Misc

• Opensearch exporter fails with 400 on AWS Opensearch service (#18251)
• [Spring Zeebe SDK] Token not refreshed (#17799)
• Broken job stream aggregation (#17513)
• Timestamp values in actuators are serialized as integers instead of date-time strings (#17347)
• Partition stays in force configuration after force failover (#17334)
• Potential duplicate PI creation across partitions in case of request timeouts (#17333)
• SetVariables is not always retryable (#15549)

Maintenance

• Setup a nightly integration workflow with a AWS Opensearch instance (#18252)
• Make Snapshot Store IO bounded instead of CPU (#17717)

Merged Pull Requests

• fix: do not retry create instance on closed connection (#18264)
• fix: add leading slash to opensearch endpoints (#18253)
• refactor: migrate test to new infrastructure (#18223)
• refactor: allow all semantic versions (#18220)
• test: disable flake BackupUploadIT.shouldSaveBackupWithManyFiles (#18205)
• test: ensure no leader before restarting outdated follower (#18203)
• fix: retry SetVariable on for UNAVAILABLE and RESOURCE_EXHAUSTED (#18180)
• Fixing token validity verification that was causing authentication error (#18166)
• Symlink .idea folder for zeebe subfolder (#18165)
• fix: go client omit optional scope param if not set (#18154)
• test: fix flaky test by buffering possibly chunked content (#17923)
• fix: Make SnapshotStore IO bounded. (#17718)
• fix: do not short-circuit retry for force configure request (#17641)
• Fix broken job stream aggregation across stream restarts (#17545)
• refactor: remove unused spring-client-common (#17503)
• fix: fix broken job lifetime metric (#17499)
• Align deployment rejection message for DMN resources (#17475)
• feat(zbctl): allows scope to be supplied via command line parameter (#17429)
• deps: Update dependency com.github.spotbugs:spotbugs-maven-plugin to v4.8.4.0 (main) (#17395)
• fix: delete existing ISM policy when retention is disabled (#17386)
• ci: cancel outdated ci runs (#17315)
• ci: rely on automatic setup of CodeQL (#17313)
• deps: Update module golang.org/x/net to v0.23.0 (main) (#17294)
• test: increase await assertion timeout in OpensearchExporterIT IndexSettingsTest to overcome flaky test runs (#17282)
• deps: bump dependency used by Azure backups to fix CVE (#17269)
• test: ensure PKCS1 support with REST (#17216)
• Soft pause information is persisted across all replicas. (#16869)

8.5.0

Enhancements

Broker

• Subscribe to a message boundary event on process instance migration (#16384)

... (truncated)

Commits

• 72bcf0e [maven-release-plugin] prepare release 8.5.1
• 88c5320 build(project): update go embedded version data
• ad505f8 deps(identity): update identity to 8.5.1
• cbcbb8f [Backport stable/8.5] fix: retry SetVariable on for UNAVAILABLE and RESOURCE_...
• da273a2 refactor: keep alphabetical order in gateway service config
• 7294737 fix: retry SetVariable on for UNAVAILABLE and RESOURCE_EXHAUSTED
• d05d646 [Backport stable/8.5] Fixing token validity verification that was causing aut...
• 0e014c8 fix: adjust test import after backport
• 6006965 [Backport stable/8.5] fix: go client omit optional scope param if not set (#1...
• a1ca7e2 [Backport stable/8.5] refactor: allow all semantic versions (#18298)
• 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

[cr-gpt[bot]]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[codesyncapp[bot]]

Check out the playback for this Pull Request here.

[git-greetings[bot]]

Thanks @dependabot[bot] for opening this PR!

For COLLABORATOR only :

• To add labels, comment on the issue /label add label1,label2,label3

• To remove labels, comment on the issue /label remove label1,label2,label3

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[git-greetings[bot]]

PR Details of @dependabot[bot] in zeebe-io-zeebe-chaos :	OPEN	CLOSED	TOTAL
7	23	30

[coderabbitai[bot]]

[!IMPORTANT]

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[guardrails[bot]]

:warning: We detected 1 security issue in this pull request:

Vulnerable Libraries (1)

Severity | Details :-: | :-- High | [pkg:golang/github.com/camunda/zeebe/clients/go/v8@v8.5.1](https://github.com/2lambda123/zeebe-io-zeebe-chaos/blob/94271e54b2c50990e8c0e4041592e21ed419b67c/go-chaos/go.mod#L6) upgrade to: *> v8.5.1* More info on how to fix Vulnerable Libraries in [Go](https://docs.guardrails.io/docs/en/vulnerabilities/go/using_vulnerable_libraries.html?utm_source=ghpr).

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[secure-code-warrior-for-github[bot]]

Micro-Learning Topic: Vulnerable library (Detected by phrase)

Matched on "Vulnerable Libraries"

What is this? (2min video)

Use of vulnerable components will introduce weaknesses into the application. Components with published vulnerabilities will allow easy exploitation as resources will often be available to automate the process.

Try a challenge in Secure Code Warrior