Skip to content

docs: Worker Versioning with Serverless Workers on AWS Lambda#4740

Open
bchav wants to merge 1 commit into
mainfrom
docs/lambda-worker-versioning
Open

docs: Worker Versioning with Serverless Workers on AWS Lambda#4740
bchav wants to merge 1 commit into
mainfrom
docs/lambda-worker-versioning

Conversation

@bchav

@bchav bchav commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds an encyclopedia section on Worker Versioning with Serverless Workers, explaining how Worker Deployment Versions map 1:1 to Lambda function versions via qualified versioned ARNs, with a Mermaid diagram of the Build ID → Lambda function version mapping.
  • Updates the AWS Lambda guide with a single aws lambda publish-version procedure that uses the qualified versioned ARN as --aws-lambda-function-arn and rolls back via temporal worker deployment set-current-version. Calls out that unqualified ARNs are acceptable for development and testing but lose Pinned's no-patching guarantee.
  • Adds a pointer from "Choosing a Versioning Behavior" in the Worker Versioning page to the new encyclopedia section.

Test plan

  • Preview deploy renders the Mermaid diagram on the Serverless Workers encyclopedia page
  • Tabs and code blocks render correctly on the AWS Lambda guide
  • Internal links from Worker Versioning → encyclopedia section resolve

🤖 Generated with Claude Code

┆Attachments: EDU-6563 docs: Worker Versioning with Serverless Workers on AWS Lambda

@bchav bchav requested a review from a team as a code owner June 17, 2026 21:36
@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
temporal-documentation Error Error Jun 18, 2026 1:12pm

Request Review

@github-actions

github-actions Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

📖 Docs PR preview links

Each Worker Deployment Version maps 1:1 to one Lambda function version via
a qualified versioned ARN. The choice applies to both Pinned and
Auto-Upgrade Workflows; Versioning Behavior controls only how Workflows
move between Worker Deployment Versions in Temporal, not how a Worker
Deployment Version targets Lambda.

- encyclopedia: new section with a Mermaid diagram of the Build ID to
  Lambda function version mapping. Qualified versioned ARNs are framed
  as the production recommendation; unqualified ARNs are noted as
  acceptable for development and testing, with the trade-off (loss of
  Pinned's no-patching guarantee) called out explicitly.
- aws-lambda guide: single procedure using `aws lambda publish-version`,
  qualified ARN as `--aws-lambda-function-arn`, and rollback via
  `temporal worker deployment set-current-version`.
- worker-versioning: pointer from "Choosing a Versioning Behavior" to
  the new encyclopedia section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

1 participant