fix _next/image test

[vicb]

Root cause is fixed at cloudflare/workers-sdk#9935

This PR should not be merged until the fix is released to miniflare

[changeset-bot]

⚠️ No Changeset found

Latest commit: bd7884f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@opennextjs/cloudflare@777

commit: bd7884f

[vicb]

Tests look good after updating Miniflare (via wrangler)

[Copilot]

Pull Request Overview

This PR fixes a test related to Next.js image handling by updating the wrangler dependency and simplifying test assertions. The changes address issues with _next/image test behavior that was previously fixed in the upstream workers-sdk repository.

• Updates wrangler version from ^4.23.0 to ^4.24.4 to include upstream fixes
• Simplifies image request test to expect a specific 400 status code instead of multiple possible status codes

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
pnpm-workspace.yaml	Updates wrangler dependency version to include upstream fixes
examples/playground14/e2e/cloudflare.spec.ts	Simplifies test assertion to expect only 400 status for disallowed image requests

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (1)

examples/playground14/e2e/cloudflare.spec.ts:31

• The test now only checks for a 400 status code, but the removed comment suggests that a 403 status from the asset worker was also a valid response. Consider adding a comment explaining why only 400 is now expected, or verify that the upstream fix ensures consistent 400 responses.

			expect(res.status()).toBe(400);

[vicb]

Thanks for the review