Versions rollback

[RamIdeas]

What this PR solves / how to test

CR: https://jira.cfdata.org/browse/CR-850334

This PR implements versioned rollbacks via wrangler rollback [version-id] --experimental-versions.

Please note, the experimental-versions flag is required to use the new behaviour and the original wrangler rollback command is unchanged if run without this flag.

Author has addressed the following

• Tests
  • TODO (before merge)
  • Included
  • Not necessary because:
• Changeset (Changeset guidelines)
  • TODO (before merge)
  • Included
  • Not necessary because:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s): Versions, Deployments, Gradual Deployments cloudflare-docs#13429
  • Not necessary because:

[changeset-bot]

🦋 Changeset detected

Latest commit: b0db6ad

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
wrangler	Minor
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-wrangler-5373

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/5373/npm-package-wrangler-5373

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-wrangler-5373 dev path/to/script.js

Additional artifacts:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-create-cloudflare-5373 --no-auto-update

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-cloudflare-kv-asset-handler-5373

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-miniflare-5373

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-cloudflare-pages-shared-5373

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8440747875/npm-package-cloudflare-vitest-pool-workers-5373

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.38.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20240320.0
workerd	1.20240320.1	1.20240320.1
workerd --version	1.20240320.1	2024-03-20

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[codecov]

Codecov Report

Attention: Patch coverage is 42.85714% with 36 lines in your changes are missing coverage. Please review.

Project coverage is 72.24%. Comparing base (7d160c7) to head (b0db6ad).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5373      +/-   ##
==========================================
- Coverage   72.29%   72.24%   -0.05%     
==========================================
  Files         318      321       +3     
  Lines       16458    16616     +158     
  Branches     4201     4253      +52     
==========================================
+ Hits        11898    12004     +106     
- Misses       4560     4612      +52     

Files	Coverage Δ
packages/wrangler/src/index.ts	90.74% <100.00%> (+0.11%)	⬆️
packages/wrangler/src/versions/deploy.ts	92.47% <100.00%> (+0.12%)	⬆️
packages/wrangler/src/versions/deployments/list.ts	100.00% <100.00%> (ø)
...ckages/wrangler/src/versions/deployments/status.ts	97.61% <100.00%> (-0.30%)	⬇️
packages/wrangler/src/yargs-types.ts	100.00% <ø> (ø)
packages/wrangler/src/versions/rollback/index.ts	21.73% <21.73%> (ø)

... and 22 files with indirect coverage changes

[mrbbot]

It might be helpful to explain what wrangler rollback [version-id] does here. I guess deploying with 100% of [version-id], or the last 100% version if [version-id] is omitted?