Skip to content

clarify historical Worker code retrieval on Versions & deployments pa…#32270

Open
dpiteira95 wants to merge 1 commit into
cloudflare:productionfrom
dpiteira95:patch-15
Open

clarify historical Worker code retrieval on Versions & deployments pa…#32270
dpiteira95 wants to merge 1 commit into
cloudflare:productionfrom
dpiteira95:patch-15

Conversation

@dpiteira95

Copy link
Copy Markdown
Contributor

…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.

…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

cloudflare-docs-bot Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 2 warnings found in commit 4b3e880.

👉 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-54ce57c9fcd6 · Unescaped angle brackets in MDX prose
- **File:** `src/content/docs/workers/versions-and-deployments/index.mdx` line 63
- **Issue:** The added sentence `You can find the <DEPLOYMENT_ID> in the Deployments tab...` contains `<DEPLOYMENT_ID>` outside a code block, so Astro/MDX will interpret it as a JSX/component tag.
- **Fix:** Wrap placeholders in backticks, e.g. `<DEPLOYMENT_ID>`, or escape the angle brackets so the text renders correctly.

---

## Style Guide Review

### Warnings (1)

#### SG-b4422ef959d3 · Terminal commands must be monospace
- **File:** `src/content/docs/workers/versions-and-deployments/index.mdx` line 63
- **Issue:** Line includes `wrangler deployments list` in prose without backticks.
- **Fix:** Change to `wrangler deployments list`.

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 63 Unescaped angle brackets in MDX prose — The added sentence You can find the <DEPLOYMENT_ID> in the Deployments tab... contains <DEPLOYMENT_ID> outside a code block, so Astro/MDX will interpret it as a JSX/component tag. Fix: Wrap placeholders in backticks, e.g. <DEPLOYMENT_ID>, or escape the angle brackets so the text renders correctly.

Conventions

No convention issues found.

Style Guide Review

Warnings (1)
File Issue
workers/versions-and-deployments/index.mdx line 63 Terminal commands must be monospace — Line includes wrangler deployments list in prose without backticks. Fix: Change to wrangler deployments list.
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:workers Related to Workers product size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants