GHA to check api-go compatibility

[rodrigozhou]

What was changed

GHA to check compatibility of api-go

Why?

Automation

Checklist

1. Closes

2. How was this tested:

3. Any docs updates needed?

[cretz]

Thanks! Note, when making the api side, you may want the ability to bypass. The reason one might want to bypass is because we know the API is incompatible and we plan on tagging a new Go SDK release with the new API release immediately after API release is complete.

[cretz]

LGTM, but a general question about moving this to api-go as there seems to be no benefit to it being in the SDK.

[cretz]

Question, can we just put this whole workflow inside of api-go? Is there any reason it needs to be inside the SDK repo?

[rodrigozhou]

@cretz Sure, I had initially put in the api repo because it's where the release process starts. Any particular reason to put in api-go instead of api?

[cretz]

Any particular reason to put in api-go instead of api?

Yes, this check is very Go specific. I know the API repo has some Go things, but in theory the API repo is supposed to be language agnostic. Having said that, if it is easier to fail the release from api instead of api-go, no problem.

[rodrigozhou]

Makes sense, moved to api-go repo: temporalio/api-go#200