Skip to content

Forward published release events to temporalio/temporal - #308

Draft
stpierre wants to merge 1 commit into
temporalio:mainfrom
stpierre:stpierre/trigger-oss-api-update-on-release
Draft

Forward published release events to temporalio/temporal#308
stpierre wants to merge 1 commit into
temporalio:mainfrom
stpierre:stpierre/trigger-oss-api-update-on-release

Conversation

@stpierre

@stpierre stpierre commented Aug 25, 2026

Copy link
Copy Markdown
Member

What changed?

This adds a GH workflow that runs when a release is published that forwards the event to temporalio/temporal.

Why?

This will let us automatically bump patch releases of the API module in OSS.

How did you test it?

Pre-merge, the workflow cannot be tested due to GH permissions. Once merged, the workflow is self-testing on future changes.

Potential risks

None; if the job fails, the release is still published and updating the API module proceeds manually.

@CLAassistant

Copy link
Copy Markdown

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.

This will let us automatically bump patch releases of the API module in OSS.
@stpierre
stpierre force-pushed the stpierre/trigger-oss-api-update-on-release branch from 8de8cca to 8ac11b6 Compare August 26, 2026 15:28
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