fix: only show fetch warning if on old compatibility_date

[petebacondarwin]

Now that we have the allow_custom_ports compatibility flag, we only need to show the fetch warnings when that flag is not enabled.

Fixes #6950

Fixes cloudflare/workerd#2955

Author has addressed the following

• 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:
• Changeset (Changeset guidelines)
  • TODO (before merge)
  • Changeset included
  • Changeset not necessary because:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: bug fix

[changeset-bot]

🦋 Changeset detected

Latest commit: d7f86a1

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

This PR includes changesets to release 2 packages

Name	Type
wrangler	Patch
@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/11795973949/npm-package-wrangler-7038

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

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

Or you can use npx with this latest build directly:

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

Additional artifacts:

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

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

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

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

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

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

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

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

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

---

[email protected] includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20241106.0
workerd	1.20241106.1	1.20241106.1
workerd --version	1.20241106.1	2024-11-06

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

[penalosa]

16 files for such a small change 😢

[ceddybi]

@petebacondarwin @penalosa not just hiding the warning, fetching with custom HTTPS port doesn't work too, looks like the port is wiped somewhere

[petebacondarwin]

@ceddybi - good point. It seems that on production this now works correctly if the compat date is new (>2024-09-01) or the compat flag is on (allow_custom_ports). But my local testing seems to show workerd crashing in Miniflare. I need to dig in why that is the case. Notwithstanding that, this PR is still valid, since in production the warning is no longer needed when the compat date/flag is setup correctly.