temporalio / roadrunner-temporal

Temporal PHP-SDK Host Process plugin for Roadrunner
MIT License
22 stars 8 forks source link

chore(deps): bump go.temporal.io/server from 1.21.5 to 1.22.0 #415

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps go.temporal.io/server from 1.21.5 to 1.22.0.

Release notes

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

v1.22.0

Release Highlights

Streaming for replication (WIP)

This version of server added gRPC streaming API for replications between clusters. This feature is still working in progress, is currently disabled by default. It will be enabled in future release.

Count workflow by ExecutionStatus

The Count API feature allows the user to count the number of workflow matching the given query. For example, the command temporal workflow count -q "WorkflowType='foo'" returns the number of workflows that matches WorkflowType='foo'.

Now, you can send queries to the Count API to group by a given search attribute. Eg: -q "WorkflowType='foo' GROUP BY ExecutionStatus returns the number of workflows that matches WorkflowType='foo' grouped by ExecutionStatus.

The GROUP BY clause is only supported in the Count API, and, at this moment, we only support grouping by ExecutionStatus. We plan to support group by any search attribute in a future release.

Default authorizer changes

The default authorizer now allows OperatorService.ListSearchAttributes as a namespace-level read-only API. Additionally, the implementation was changed: if you have custom authorizer code based on the default authorizer, you may want to examine the new implementation.

Schedules improvements

Schedules that are “idle”, meaning they are only configured to run for a fixed number of times (either with “limited actions” or with a spec that doesn’t match any times in the future), will now automatically be deleted after one week since their last action. This applies to existing schedules, however existing schedules that are already idle won’t be deleted unless they’re woken up by a signal.

Jitter is now calculated correctly so that jitter across separate schedules is not correlated. This automatically applies to existing schedules.

HTTP API

The frontend workflow service API can now exposed via HTTP in addition to the existing gRPC exposed form. The port is set on services.frontend.rpc.httpPort and is disabled if unset or 0. The default Docker template enables the HTTP API on port 7243. See the HTTP annotations on the workflow service API proto file for more information about which operations are available at which URL paths.

All changes

2023-09-05 - 9b877fae2 - increase max allowed shard linger limit (#4790) 2023-09-05 - c73430b8a - Mark QueryWorkflow as read-only in api metadata (#4834) 2023-09-05 - 86d883913 - Add method metadata and use for default authorizer (#4794) 2023-08-28 - bba21caee - Always persist guessed set id on unknown build id (#4800) 2023-08-28 - c13afdcef - Fix mutable state change not persisted bug (#4813) 2023-08-21 - df2167ef0 - Update API to v1.24.0 (#4785) 2023-08-21 - f6755a53c - Return NonRetryableApplicationError if Namespace is not found on remote cluster during verify (#4786) 2023-08-21 - f42d19eba - Split sync workflow state logic to dedicated file (#4784) 2023-08-18 - c7847968b - HTTP API support (#4543) 2023-08-17 - 8309152e1 - Update some task refresh logic (#4779) 2023-08-17 - 0080bd209 - Simplify XDC logic (#4546) 2023-08-14 - 84b1e8b5a - Generate txn id for each event (#4774) 2023-08-14 - aa5c3db6f - Add api to Eager retrieve the unknown namespace from remote cluster (#4769) 2023-08-14 - 9f9db3f06 - Increaes RecordHeartbeat frequency in VerifyReplicationTask (#4771) 2023-08-11 - 815c8a359 - Skip verifying workflow which has already passed retention time (#4770) 2023-08-11 - 0ce1234ee - Rename leftover master to main (#4768) 2023-08-11 - 7982f81e4 - Fix delete search attributes in mutable state (#4767) 2023-08-11 - 545c96378 - Count group by status capability (#4750) 2023-08-11 - 88f8c1c66 - Load task queue managers for demoted version set ids (#4762)

... (truncated)

Commits


Dependabot compatibility score

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)
CLAassistant commented 1 year ago

CLA assistant check
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 commented 1 year ago

CLA assistant check
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.

dependabot[bot] commented 1 year ago

Looks like go.temporal.io/server is up-to-date now, so this is no longer needed.