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

Use the new temporalproto JSON APIs #375

Merged
merged 4 commits into from
Nov 29, 2023

Conversation

tdeebswihart
Copy link
Contributor

What was changed

I bumped the version of the SDK and API to make use of our new temporalproto APIs

Why?

We made a breaking change in the API

@@ -141,7 +141,7 @@ jobs:
# TODO: Find some way to automatically upgrade to "latest"
with:
do-push: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
go-repo-ref: 'f9d73bfdf7c8d3ec0311306140fbfafa7fb6f9cf'
go-repo-ref: '8f2a3c8f967a5898f45df92f6bc42196e4702a2d'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the first version of the SDK that uses the new APIs

These offer better performance than the previous versions.
@tdeebswihart tdeebswihart force-pushed the tdeebswihart/use-new-temporalproto-api branch from bde2815 to 8d9d173 Compare November 28, 2023 19:37
@@ -9,7 +9,7 @@ require (
github.com/temporalio/features/features v1.0.0
github.com/temporalio/features/harness/go v1.0.0
github.com/urfave/cli/v2 v2.25.7
go.temporal.io/sdk v1.25.2-0.20231121222453-f9d73bfdf7c8
go.temporal.io/sdk v1.25.2-0.20231129163633-77626eee3015
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not the biggest fan of using untagged SDKs in the features repo main branch. But I guess we had already done it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. As we discussed (this is for public record, hello!) I'm going to merge from now to keep usage simple since this is a breaking change that hit both the SDK and the Server, but will do so next time.

@tdeebswihart tdeebswihart merged commit f726432 into main Nov 29, 2023
17 checks passed
@tdeebswihart tdeebswihart deleted the tdeebswihart/use-new-temporalproto-api branch November 29, 2023 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants