chore(deps): bump go.temporal.io/server from 1.18.1 to 1.18.2

[dependabot[bot]]

Bumps go.temporal.io/server from 1.18.1 to 1.18.2.

Release notes

Sourced from go.temporal.io/server's releases.

v1.18.2

Release Highlights

This patch releases fixes a few small bugs in namespace migration. It also has two changes to scavengers: the history scavenger is now enabled on SQL persistence, and the execution scavenger now finds mutable state that's past its retention timeout.

All Changes

2022-10-17 - 1b8e28f64 - Implement GetAllHistoryTreeBranches for SQL persistence backends (#3438) 2022-10-17 - 2127976bf - Properly handle min task ID > max task ID case during shard re-balancing (#3470) 2022-10-17 - d602bff22 - Fix timer task visibility timestamp for workflow refresh (#3460) 2022-10-17 - 8cd481ad7 - Fix scheduled queue max read level update for single processor (#3474) 2022-10-17 - 45bd55d02 - Turns on the history scavenger for SQL backends (#3462) 2022-10-17 - bb7b1f432 - Fix sanitize mutable state after replication (#3479) 2022-10-17 - ff47b2c3c - Add execution scavenger for retention (#3457) 2022-10-17 - 78366f1e5 - Update replication timestamp with no task (#3487) 2022-10-17 - b57b9307b - Do not add version 0 to failover history (#3483) 2022-10-18 - 9a427c26a - Rewrite mysql PaginateBranchesFromHistoryTree query (#3509) 2022-10-18 - 07ab3e111 - Warning log on new event during set workflow (#3508) 2022-10-18 - 0aa594887 - Update version to 1.18.2

Details about the v1.18.0 release can be found here.

Helpful links to get you started with Temporal

Temporal Docs Server Docker Compose Helm Chart

Docker images for this release (use tag 1.18.2)

Server Server With Auto Setup (what is Auto-Setup?) Admin-Tools

Commits

• 0aa5948 Update version to 1.18.2
• 07ab3e1 Warning log on new event during set workflow (#3508)
• 9a427c2 Rewrite mysql PaginateBranchesFromHistoryTree query (#3509)
• b57b930 Do not add version 0 to failover history (#3483)
• 78366f1 Update replication timestamp with no task (#3487)
• ff47b2c Add execution scavenger for retention (#3457)
• bb7b1f4 Fix sanitize mutable state after replication (#3479)
• 45bd55d Turns on the history scavenger for SQL backends (#3462)
• 8cd481a Fix scheduled queue max read level update for single processor (#3474)
• d602bff Fix timer task visibility timestamp for workflow refresh (#3460)
• 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)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}