Redo activity HTTP APIs #716
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cretz
approved these changes
Feb 11, 2026
Member
cretz
left a comment
cretz
left a comment
There was a problem hiding this comment.
Can we add a 💥 to PR description and make sure to update release notes with a big compat note in this repo and in api-go?
harani-mukkala
approved these changes
Feb 11, 2026
harani-mukkala
left a comment
harani-mukkala
left a comment
There was a problem hiding this comment.
Since this introduces a breaking change to the experimental API, do we have a way to verify that these endpoints haven’t received significant traffic in the past few days?
Member
Author
|
These endpoints are not available in Temporal cloud and we can't tell what self-hosted users are doing. |
6 tasks
bergundy
added a commit
that referenced
this pull request
Feb 11, 2026
💥 **BREAKING CHANGE** 💥 **What changed?** - Redefined the experimental activity HTTP API paths. - The activity operator APIs were explicitly marked as deprecated, they will be redone when we add support for standalone activities. - All verbs that didn't have an identifier in the path (e.g. APIs that take a token), were renamed `activity-$VERB`. - All APIs that take identifiers (either within a workflow or for standalone) were restructured to include the identifiers in the path. - Chose the name `resolve-as-canceled` for `RespondActivityTaskCanceledById` to prevent the collision with `cancel` with maps to `RequestCancelActivityExecution`, which matches the path verb for `RequestCancelWorkflowExecution`. **Why?** The existing API paths have conflicts and aren't usable. Consistency and future proofing. **Breaking changes** Yes, but the HTTP API is experimental. **Server PR** Not needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
💥 BREAKING CHANGE 💥
What changed?
activity-$VERB.resolve-as-canceledforRespondActivityTaskCanceledByIdto prevent the collision withcancelwith maps toRequestCancelActivityExecution, which matches the path verb forRequestCancelWorkflowExecution.Why?
The existing API paths have conflicts and aren't usable. Consistency and future proofing.
Breaking changes
Yes, but the HTTP API is experimental.
Server PR
Not needed.