Skip to content

Run CI on behalf of #9416 @8e930470c230bae6c7e58bf888d7619c4385d934#9491

Closed
github-actions[bot] wants to merge 7 commits intomainfrom
run-ci-on-behalf-of-9416
Closed

Run CI on behalf of #9416 @8e930470c230bae6c7e58bf888d7619c4385d934#9491
github-actions[bot] wants to merge 7 commits intomainfrom
run-ci-on-behalf-of-9416

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jun 5, 2025

This PR runs CI on behalf of #9416 at commit 8e93047. It can be closed after the CI run is complete.

- When a request matches a static routing "exclude" rule, it's directly
forwarded to the asset worker.

- When a request matches a static routing "include" rule, it's directly
forwarded to the user worker.

- Otherwise, previous behavior takes over

This also adds a new analytics field (double6) for what routing decision
was made
vitest yelled at me and told me this should be awaited and may error in
future releases
When the Router worker has static routing, the check against
"Sec-Fetch-Mode: navigate" is unnecessary. We have explicit static
routing to indicate whether or not we should go to a User worker or
the Asset worker, and should not try and guess via usually-set browser
headers

This adds a new parameter to unstable_canFetch RPC method, which should
be fine for backwards compatibility, and can be extended in the future
if needed. This was necessary because the Asset worker checks the
Request headers for Sec-Fetch-Mode to indicate if it can serve an asset
(including an index.html or 404.html page based on not_found_handling),
but static routing is only provided to the Router worker. Thus, we need
to pass more information over RPC
@github-actions github-actions bot added the e2e Run wrangler + vite-plugin e2e tests on a PR label Jun 5, 2025
@changeset-bot
Copy link

changeset-bot bot commented Jun 5, 2025

🦋 Changeset detected

Latest commit: d5c5255

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

This PR includes changesets to release 1 package
Name Type
@cloudflare/workers-shared Minor

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

Now that we're not providing this configuration via _routes.json, we can
relax some of the configuration. Much of this happens on the backend,
but some field names have been changed ("include" -> "worker",
"exclude"->"asset") asdfasdf
@emily-shen emily-shen force-pushed the run-ci-on-behalf-of-9416 branch from 8e93047 to d5c5255 Compare June 5, 2025 10:53
@github-project-automation github-project-automation bot moved this to Untriaged in workers-sdk Jun 5, 2025
@emily-shen emily-shen added the c3-e2e Run c3 e2e tests on a PR label Jun 5, 2025
@github-actions
Copy link
Contributor Author

github-actions bot commented Jun 5, 2025

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/15465190111/npm-package-wrangler-9491
Prereleases for other packages:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/15465190111/npm-package-cloudflare-workers-bindings-extension-9491 -O ./cloudflare-workers-bindings-extension.0.0.0-va9c0f63c9.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-va9c0f63c9.vsix

create-cloudflare:

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

@cloudflare/kv-asset-handler:

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

miniflare:

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

@cloudflare/pages-shared:

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

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/15465190111/npm-package-cloudflare-unenv-preset-9491

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/15465190111/npm-package-cloudflare-vite-plugin-9491

@cloudflare/vitest-pool-workers:

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

@cloudflare/workers-editor-shared:

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

@cloudflare/workers-shared:

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

@cloudflare/workflows-shared:

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

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

@github-project-automation github-project-automation bot moved this from Untriaged to Done in workers-sdk Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c3-e2e Run c3 e2e tests on a PR e2e Run wrangler + vite-plugin e2e tests on a PR

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants