Closed dario-piotrowicz closed 3 days ago
Latest commit: bc719b8d8dc999a5d36778863d130f4a46aee900
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.
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
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/9695301620/npm-package-wrangler-6159
You can reference the automatically updated head of this PR with:
npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6159/npm-package-wrangler-6159
Or you can use npx
with this latest build directly:
npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9695301620/npm-package-wrangler-6159 dev path/to/script.js
wrangler@3.62.0
includes the following runtime dependencies:
Package | Constraint | Resolved |
---|---|---|
miniflare |
workspace:* | 3.20240620.0 |
workerd |
1.20240620.1 | 1.20240620.1 |
workerd --version |
1.20240620.1 | 2024-06-20 |
Please ensure constraints are pinned, and miniflare
/workerd
minor versions match.
Will this break a test?
oh.... I didn't think of that....
I can't see the string being tested anywhere:
So I think that it should be fine 🙂
What this PR solves / how to test
Just fixing a typo I noticed when running
wrangler pages deploy
Author has addressed the following