Closed CarmenPopoviciu closed 5 days ago
Latest commit: f4c7a9cf33f31b38eb042cc43e2e442d95c333ff
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/9660938980/npm-package-wrangler-6139
You can reference the automatically updated head of this PR with:
npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6139/npm-package-wrangler-6139
Or you can use npx
with this latest build directly:
npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/9660938980/npm-package-wrangler-6139 dev path/to/script.js
wrangler@3.61.0
includes the following runtime dependencies:
Package | Constraint | Resolved |
---|---|---|
miniflare |
workspace:* | 3.20240610.1 |
workerd |
1.20240610.1 | 1.20240610.1 |
workerd --version |
1.20240610.1 | 2024-06-10 |
Please ensure constraints are pinned, and miniflare
/workerd
minor versions match.
What this PR solves / how to test
C3 astro e2e test started failing in CI for no obvious reasons since Mon 24 June 2024. We tried everything, like increasing timeouts, debugging, reproducing locally (which we can't) to no avail. We are quite confident that the test failures are not caused by any changes in wrangler (we verified this by running the tests against a PR where they were consistently green, but did fail on the re-run, without any changes to the branch).
As this is blocking our release, we decided to quarantine these tests, do the release, while continuing to look into why the tests are failing.
Author has addressed the following