Skip to content

Inherit pinned deployment version from parent workflow#549

Merged
ShahabT merged 1 commit intoversioning-3.1from
shahab/pinned-child
Feb 5, 2025
Merged

Inherit pinned deployment version from parent workflow#549
ShahabT merged 1 commit intoversioning-3.1from
shahab/pinned-child

Conversation

@ShahabT
Copy link
Copy Markdown
Contributor

@ShahabT ShahabT commented Feb 5, 2025

READ BEFORE MERGING: All PRs require approval by both Server AND SDK teams before merging! This is why the number of required approvals is "2" and not "1"--two reviewers from the same team is NOT sufficient. If your PR is not approved by someone in BOTH teams, it may be summarily reverted.

What changed?
Child workflows start in parent's pinned Worker Deployment Version.

Why?
So user do not have to worry about interface compatibility between pinned parents and children.

Breaking changes

Server PR

@ShahabT ShahabT requested review from a team as code owners February 5, 2025 17:46
@ShahabT ShahabT merged commit 5e42a96 into versioning-3.1 Feb 5, 2025
@ShahabT ShahabT deleted the shahab/pinned-child branch February 5, 2025 22:00
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