Shorten workflow history identifiers - #507
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
longquanzheng
force-pushed
the
codex/shorten-workflow-history-names
branch
from
September 18, 2026 20:02
dc2d90d to
7c64c00
Compare
longquanzheng
force-pushed
the
codex/shorten-workflow-history-names
branch
from
September 18, 2026 20:16
7c64c00 to
09d4fd6
Compare
longquanzheng
marked this pull request as ready for review
September 18, 2026 20:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Breaking change
Running workflows and histories created with the former internal names are intentionally unsupported. This change adds no Temporal/Cadence version gate, old-name alias, or compatibility path, and does not increment GlobalVersioner.
Validation
make -C server unitTestsmake -C server temporalIntegTestsmake -C server cadenceIntegTests integrationCoverageArgs="-search=false"make -C server replayTestsmake copyright-checkcd docs && npm run checkThe monolithic local
ci-all-teststarget exceeds its package-level 20-minute limit when both backend suites run together; its default Cadence search-pagination cases also hit the existing local Elasticsearch visibility delay. The backend suites pass independently with the same search setting used by the Cadence CI shard. The locallinttarget cannot start onorigin/mainbecause.build/proto-lintis absent.No files under
protos/, SDKs, or the Web frontend changed.