clarify historical Worker code retrieval on Versions & deployments pa…

[dpiteira95]

…ge.mdx

Users frequently need to audit or retrieve the code from a previous Worker deployment, for example during a security investigation. The current Versions & deployments page implies that the dashboard andWrangler provide full visibility into historical deployments, but neither exposes the actual code of a previous deployment.

This change:

• Clarifies that Wrangler's deployments list and versions list commands return metadata only .
• Clarifies that the dashboard Deployments tab shows deployment history and IDs, but not the code of previous deployments.
• Adds a "Retrieve code from a previous deployment" subsection with the Cloudflare API call that can be used to fetch a specific deployment's bundled code.

This helps customers understand the correct workflow and avoids the assumption that historical code can be retrieved through Wrangler or the dashboard alone.

[cloudflare-docs-bot]

Review

⚠️ 1 warning found in commit 4dd9334.

👉 Fix in your agent 👈

Fix the following review findings in PR #32270 (https://github.com/cloudflare/cloudflare-docs/pull/32270).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Warnings (1)

#### CR-5578f52166cb · Incorrect factual claim
- **File:** `src/content/docs/workers/versions-and-deployments/index.mdx` line 44
- **Issue:** The added sentence says Wrangler "allows you to view the 100 most recent versions and deployments," but the page it links to (`/workers/wrangler/commands/workers/#versions-list`) documents `versions list` as "Retrieve details for the 10 most recent versions." The "100 most recent" figure elsewhere in the docs (rollbacks.mdx) refers to the rollback/promotion limit, not to what `wrangler versions list` / `wrangler deployments list` display, so the claim is inaccurate and contradicts the linked reference.
- **Fix:** Reword to match the linked command docs, e.g. "Wrangler allows you to view the 10 most recent versions and deployments via `wrangler versions list` and `wrangler deployments list`." If a higher limit is intended, state it per command and update the linked `versions list` description to match.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)

File

Issue

workers/versions-and-deployments/index.mdx line 44

Incorrect factual claim — The added sentence says Wrangler "allows you to view the 100 most recent versions and deployments," but the page it links to (/workers/wrangler/commands/workers/#versions-list) documents versions list as "Retrieve details for the 10 most recent versions." The "100 most recent" figure elsewhere in the docs (rollbacks.mdx) refers to the rollback/promotion limit, not to what wrangler versions list / wrangler deployments list display, so the claim is inaccurate and contradicts the linked reference. Fix: Reword to match the linked command docs, e.g. "Wrangler allows you to view the 10 most recent versions and deployments via wrangler versions list and wrangler deployments list." If a higher limit is intended, state it per command and update the linked versions list description to match.

Conventions

_{No convention issues found.}

Style Guide Review

_{No style-guide issues found.}

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

[github-actions]

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).