docs: update TS Worker Docker images from EOL Debian bullseye to bookworm

[thiagojv]

Summary

Update the TypeScript SDK Worker Docker guide to stop recommending Debian bullseye-based images and use bookworm instead.

Changes in docs/develop/typescript/workers/run-process.mdx:

• node:20-bullseye -> node:20-bookworm
• node:20-bullseye-slim -> node:20-bookworm-slim
• gcr.io/distroless/nodejs20-debian11 -> gcr.io/distroless/nodejs20-debian12

Why

Debian 11 (bullseye) has reached end-of-life for standard support, so the docs should point readers at a currently supported base image. Debian 12 (bookworm) is the current stable release. The node:20-bookworm, node:20-bookworm-slim, and gcr.io/distroless/nodejs20-debian12 tags are official, published, and drop-in replacements, so the surrounding guidance (glibc requirement, ca-certificates on slim images, distroless multi-stage build) stays accurate.

Testing

• Docs-only change limited to code blocks and inline references; no prose/structure changes.
• Verified no other bullseye/debian11 references remain in the file.

Risks

Low. The guidance and Dockerfile structure are unchanged; only the base image tags are updated to their supported equivalents.

[vercel]

@thiagojv is attempting to deploy a commit to the Temporal Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-10T14:31:32.865569Z	ec15e7f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Duncanma]

Thanks for this — clean, well-scoped fix.

Review notes:

• Checked the rest of docs/ for other bullseye/debian11 references: none outside this file, and this PR's diff covers every instance in run-process.mdx. No collateral changes needed.
• No structural or tone issues — this is a straight tag swap inside existing code blocks, no prose or heading changes.

Worth considering (not a blocker): Debian 13 (trixie) has been the current stable release since August 2025 — bookworm is now oldstable (LTS-supported until 2028). Both node:20-trixie and gcr.io/distroless/nodejs20-debian13 are already published. bookworm is still a perfectly reasonable, well-supported choice (and arguably more conservative than jumping straight to the newest release), but wanted to flag it in case you'd rather target trixie directly so this doesn't need a follow-up in a year.

One more thing: the CLA check above is still showing as not signed — could you sign the Contributor License Agreement? We won't be able to merge until that's done.

[thiagojv]

Thanks a lot for the thorough review, @Duncanma — really appreciate it!

Good call on trixie. I fully agree it's the current stable and a valid target. I intentionally went with bookworm here to stay conservative and avoid jumping two Debian releases at once: since the previous guidance was still on the EOL bullseye, moving to bookworm keeps this a minimal, low-risk drop-in swap that's easy to verify. Targeting trixie directly feels like a good follow-up once there's appetite for it, rather than bundling the extra jump into this fix. Happy to open that follow-up (or switch this PR to trixie) if you'd prefer.

Also, the CLA is signed now — the license/cla check is green. Thanks again!