Add upgrade-on-continue-as-new snippet for docs

[bchav]

Summary

• Add Go code sample for "upgrade on continue-as-new" pattern
• Snippet ID: upgrade-on-continue-as-new-go
• Will be synced to worker-versioning docs via snipsync

Context

The worker-versioning docs (PR temporalio/documentation#4148) need a snipsync-integrated code sample for the "Upgrading on Continue-as-New" section. This snippet demonstrates how pinned Workflows can detect new Worker Deployment Versions and upgrade at Continue-as-New boundaries.

Source

Based on: temporalio/sdk-go@f431242

Files Added

• features/deployment_versioning/upgrade_on_continue_as_new/feature.go - Go snippet with snipsync markers
• features/deployment_versioning/upgrade_on_continue_as_new/README.md - Description

Usage in Docs

<!--SNIPSTART upgrade-on-continue-as-new-go-->
<!--SNIPEND-->

---

Generated with Claude Code

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cretz]

The features repo is for asserting conformance across languages. It's basically a test suite. There is no assertion aspect or even use of this workflow. I wonder if samples-go would fit what you're wanting a bit more.

[THardy98]

Tested using:

go run . run --lang go --version ../sdk-go --server localhost:7233 --namespace default features/deployment_versioning/upgrade_on_continue_as_new 0

where ../sdk-go was pointed at commit for temporalio/sdk-go#2171 and local server run using latest commit of CLI, which includes the upgrade on CAN server changes

[cretz]

Is it safe to assume this same feature will be added for other langs?

[THardy98]

Is it safe to assume this same feature will be added for other langs?

Sure at some point. I'm not sure what the urgency is here @bchav . We're working on adding upgrade on CAN to the SDKs at the moment, can this wait until then or do you want the Go snippet out ASAP once the Go SDK implementation is merged/released