refactor!: remove the GetVersion gates for activity inputs and activity names by YJ-928 · Pull Request #626 · zigflow/zigflow · GitHub
Skip to content

refactor!: remove the GetVersion gates for activity inputs and activity names - #626

Merged
mrsimonemms merged 1 commit into
mainfrom
refactor/drop-version-gates
Oct 12, 2026
Merged

mrsimonemms merged 1 commit into
mainfrom
refactor/drop-version-gates

Conversation

@YJ-928

@YJ-928 YJ-928 commented Oct 12, 2026

Copy link
Copy Markdown
Member

Removes the two workflow-versioning gates, as agreed on #525: before v1.0.0, incompatible changes ship in a minor release and are listed in the release notes, so the code kept only to replay histories from earlier versions goes.

Gate Introduced by Removed
zigflow.resolve-activity-inputs #615 the change ID and version, the legacy path in activityArgs, and the test that pinned it
zigflow.per-task-activity-aliases the per-task activity names dispatchActivityName, the five legacyCall*ActivityName constants, the run builder's legacy name, and task_builder_replay_test.go

New executions behave exactly as before: activity inputs are resolved in the workflow, and activities are scheduled under their per-task names.

Breaking change (for the release notes): executions started on an earlier version of Zigflow must finish, or keep running on workers pinned with Worker Versioning, before workers are upgraded to this version.

Left in place, as a question: cmd/run/workers.go still registers the method-named activities (CallHTTPActivity, …) through ActivitiesList. Nothing schedules them after this change, but a call: activity task can still name them, so removing that registration would change behaviour for such a workflow. Happy to remove it here or in a follow-up if you'd prefer.

Relationship to #624: independent. No file overlap, and #624 uses nothing this removes. I merged both together locally: build, vet, the unit and race tests, and lint all pass, so they can merge in either order.

Verified:

  • go build ./..., go vet, golangci-lint (0 issues), gofumpt
  • the unit tests, plus -race on tasks, utils and activities
  • pre-commit on the commit (all hooks pass, including toodaloo)
  • the central e2e suite against Temporal

/cc @mrsimonemms @ShlomitSibony

…ty names

Drop the two workflow-versioning gates, zigflow.resolve-activity-inputs and
zigflow.per-task-activity-aliases, as the maintainers agreed: before v1.0.0,
incompatible changes ship in a minor release and are listed in the release
notes, so the code paths kept only to replay histories from earlier versions
are removed.

New executions behave as before: activity inputs are resolved in the workflow,
and activities are scheduled under their per-task names.

BREAKING CHANGE: executions started on an earlier version of Zigflow must
finish, or keep running on workers pinned with Worker Versioning, before
workers are upgraded to this version.
Refs: #525
Signed-off-by: Yash B Joshi <68319416+YJ-928@users.noreply.github.com>
@YJ-928
YJ-928 requested a review from a team October 12, 2026 05:37
@YJ-928 YJ-928 self-assigned this Oct 12, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Codex PR Review

No blocking issues. Ship it.

The replay compatibility break is explicitly documented in the commit: existing executions must finish or remain on pinned workers before upgrading.

Tests could not be run because the read-only environment prevents Go from creating its module cache.

@github-actions

Copy link
Copy Markdown
Contributor

@mrsimonemms
mrsimonemms added this pull request to the merge queue Oct 12, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to Branch Protection failures Oct 12, 2026
You're not authorized to push to this branch. Visit "About protected branches" for more information.
@mrsimonemms
mrsimonemms merged commit 22e196f into main Oct 12, 2026
21 checks passed
@mrsimonemms
mrsimonemms deleted the refactor/drop-version-gates branch October 12, 2026 08:25
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