Conversation
🦋 Changeset detectedLatest commit: 0e311e4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 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 |
|
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/13032244342/npm-package-wrangler-7889You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7889/npm-package-wrangler-7889Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-wrangler-7889 dev path/to/script.jsAdditional artifacts:cloudflare-workers-bindings-extension: wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-workers-bindings-extension-7889 -O ./cloudflare-workers-bindings-extension.0.0.0-vd11e670fb.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-vd11e670fb.vsixcreate-cloudflare: npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-create-cloudflare-7889 --no-auto-update@cloudflare/kv-asset-handler: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-kv-asset-handler-7889miniflare: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-miniflare-7889@cloudflare/pages-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-pages-shared-7889@cloudflare/unenv-preset: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-unenv-preset-7889@cloudflare/vite-plugin: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-vite-plugin-7889@cloudflare/vitest-pool-workers: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-vitest-pool-workers-7889@cloudflare/workers-editor-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-workers-editor-shared-7889@cloudflare/workers-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-workers-shared-7889@cloudflare/workflows-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13032244342/npm-package-cloudflare-workflows-shared-7889Note that these links will no longer work once the GitHub Actions artifact expires.
Please ensure constraints are pinned, and |
21a58b5 to
774721e
Compare
There was a problem hiding this comment.
Do we care that limitCalls = true changes technically breaks existing behaviour a bit? Previously this would (slowly) get all databases, now this only gets 30.
can we pass in a larger page size (it's 10 by default) - i tested it at 100 and it didn't seem to be noticably slower.
There was a problem hiding this comment.
This is a bit of a hack for now. Once the new API is ready we can switch over to that, which should be today or tomorrow
There was a problem hiding this comment.
Is the new API ready yet? Do we wanna wait for it or merge this as is?
There was a problem hiding this comment.
It's ready now, so I'll update this PR to use it now
edmundhung
left a comment
There was a problem hiding this comment.
Looks good to me. Just two minor comments.
There was a problem hiding this comment.
Is the new API ready yet? Do we wanna wait for it or merge this as is?
There was a problem hiding this comment.
Nit: Just find the syntax a little bit strange 😅
| getFlag("RESOURCES_PROVISION") | |
| ? await provisionBindings( | |
| bindings, | |
| accountId, | |
| scriptName, | |
| props.experimentalAutoCreate, | |
| props.config | |
| ) | |
| : null; | |
| if (getFlag("RESOURCES_PROVISION")) { | |
| await provisionBindings( | |
| bindings, | |
| accountId, | |
| scriptName, | |
| props.experimentalAutoCreate, | |
| props.config | |
| ); | |
| } |
87ed74f to
04f1a47
Compare
| "wrangler": patch | ||
| --- | ||
|
|
||
| feat: add resource auto-provisioning to versions upload |
There was a problem hiding this comment.
Should we make it clear that this is still experimental and requires an experimental flag
Allows resource provisioning in versions upload.
Also allow switching jurisdictions (since apparently buckets with the same name can exist in different jurisdictions).