Adding wrangler commands for R2 bucket lock rule configuration

[jkoe-cf]

What this PR solves / how to test
Allows user to configure lock configuration on an R2 bucket

---

• Tests
  • TODO (before merge)
  • Tests included
  • Tests not necessary because:
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required
  • Not required because: changes covered by unit tests
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s): Document wrangler r2 lock command (list, add, remove, set) cloudflare-docs#19846
  • Documentation not necessary because:

[changeset-bot]

🦋 Changeset detected

Latest commit: f53b59d

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/13549688131/npm-package-wrangler-7977

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

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

Or you can use npx with this latest build directly:

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

Additional artifacts:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13549688131/npm-package-cloudflare-workers-bindings-extension-7977 -O ./cloudflare-workers-bindings-extension.0.0.0-v00f0bc929.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-v00f0bc929.vsix

create-cloudflare:

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

@cloudflare/kv-asset-handler:

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

miniflare:

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

@cloudflare/pages-shared:

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

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13549688131/npm-package-cloudflare-unenv-preset-7977

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13549688131/npm-package-cloudflare-vite-plugin-7977

@cloudflare/vitest-pool-workers:

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

@cloudflare/workers-editor-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13549688131/npm-package-cloudflare-workers-editor-shared-7977

@cloudflare/workers-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13549688131/npm-package-cloudflare-workers-shared-7977

@cloudflare/workflows-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13549688131/npm-package-cloudflare-workflows-shared-7977

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

---

wrangler@3.110.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20250214.1
workerd	1.20250214.0	1.20250214.0
workerd --version	1.20250214.0	2025-02-14

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

[emily-shen]

would also be good to get some tests for invalid input 🧡

[emily-shen]

Also, its best practice to refrain from squashing your commits/force pushing after a review, so the reviewer can see what has changed since 🧡
If you want to tidy up your commit history you can do that after approval, but also we squash merge to main in this repo anyway so it doesn't really matter a whole lot here 🧡

[emily-shen]

nit: this is not necessary, because if the input isn't a number yargs will have failed already when its passing the cli args

[emily-shen]

nit - yargs will have set the type of lockDays as a number, so there's no need to cast this to a number again. typescript would have let you know if the type was wrong :)

[jkoe-cf]

Not sure if it's something with the test setup vs. how wrangler works in practice but it looks like it still reaches there if the type is wrong so I might leave the NaN logic as-is if that's ok

workers-sdk/packages/wrangler/src/__tests__/r2.test.ts

Line 2565 in 99db3e4

`[Error: Days must be a number.]`