Skip to content

Forward published release events to temporalio/temporal - #308

Open
stpierre wants to merge 2 commits into
temporalio:mainfrom
stpierre:stpierre/trigger-oss-api-update-on-release
Open

Forward published release events to temporalio/temporal#308
stpierre wants to merge 2 commits 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

CLAassistant commented Aug 25, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

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
@stpierre
stpierre marked this pull request as ready for review September 3, 2026 16:16
@stpierre
stpierre requested review from a team as code owners September 3, 2026 16:16
# this job needs. api-go is public, so they do happen.
if: >-
(github.event_name == 'pull_request' &&
github.event.pull_request.head.repo.full_name == github.repository) ||

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Does this need to check owner as well?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

github.repository and github.event.pull_request.head.repo.full_name are both fully-qualified owner/repo already, so it does.

(github.event_name == 'pull_request' &&
github.event.pull_request.head.repo.full_name == github.repository) ||
(github.event_name == 'release' &&
!github.event.release.draft &&

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Can this (or should this) check the event type as published?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It can, but published is already the only type that triggers this WF (line 16).

@stpierre
stpierre requested a review from tdyas September 4, 2026 21:15
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.

3 participants