Fetch script metadata directly instead of listing all scripts - #15132
Conversation
🦋 Changeset detectedLatest commit: dc757b4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
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 |
|
All changesets look good |
|
So My analysis is complete. The change is well-implemented:
I found no logic bugs, security issues, backward-compatibility violations, or incorrect API behavior. The behavior for the "script not found" case (apply all migrations) is preserved: previously LGTM |
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
aca2d32 to
dc757b4
Compare
When resolving Durable Object migrations, fetch the specific script's service metadata via
/workers/services/{name}instead of listing all scripts in the account via/workers/scripts. This avoids downloading metadata for every Worker in the account just to find one script's migration tag.A picture of a cute animal (not mandatory, but encouraged)