🦋 Changeset detected

Latest commit: b84b753

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

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

Failed to automatically backport this PR's changes to Wrangler v3. Please manually create a PR targeting the v3-maintenance branch with your changes. Thank you for helping us keep Wrangler v3 supported!

Depending on your changes, running git rebase --onto v3-maintenance main emily/dockerfile-change might be a good starting point.

Notes:

• your PR branch should be named v3-backport-10248
• add the skip-v3-pr label to the current PR to stop this workflow from failing

npm i https://pkg.pr.new/create-cloudflare@10248

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@10248

npm i https://pkg.pr.new/miniflare@10248

npm i https://pkg.pr.new/@cloudflare/pages-shared@10248

npm i https://pkg.pr.new/@cloudflare/unenv-preset@10248

npm i https://pkg.pr.new/@cloudflare/vite-plugin@10248

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@10248

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@10248

npm i https://pkg.pr.new/wrangler@10248

commit: b84b753

For posterity, I've ended up removing the e2e tests that check this behaviour because I can't get them to work in CI :( (regular unit tests still exist for this feature, the e2e tests worked locally too fwiw...)

I think this is ok because I added the e2e tests because i thought it would be useful to test the actual behaviour of docker manifest inspect since that was experimental, but we don't control the docker version in github CI anyway (e.g. currently the runners are using a version from March still). Also, if the command breaks, it doesn't break anyone's flow, it just means slightly worse DX as there is an unnecessary push.