-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
What versions & operating system are you using?
npx wrangler (latest)
Apple M4
32GB
macOS 15.6
Please provide a link to a minimal reproduction
No response
Describe the Bug
I have a PR that introduced some durable objects... It hasn't merged to main yet. But now I cannot deploy my main branch because it expects the DOs to exist that aren't on that branch yet—even though it is logically impossible to use them "before they exist". Panicking in that condition really sucks from a developer standpoint. It should ignore DOs that are "there" but undeclared in the TOML. They won't be used anyway. As is, (correct me if i am wrong) means that we cannot test anything before landing it on prod!!! For example, to get my main branch working for trivial deploys that were working yesterday, I am going to have to merge my totally unstable DOs from the new PR, way prematurely, ALL the way to my users, just to get what was working yesterday working again. OR I am going to have to down-migrate my main branch with delete_class
even though it hasn't had that DO ever? which seem pretty incoherent. This is frustrating
Please provide any relevant error logs
14:05:26.837 | -- | -- 14:05:26.876 | Total Upload: 2129.79 KiB / gzip: 365.03 KiB 14:05:37.357 | ✘ [ERROR] A request to the Cloudflare API (/accounts/075a4041877fb6b6ba069fa969244314/workers/scripts/lilthorny/versions) failed. 14:05:37.357 | 14:05:37.357 | New version of script does not export class 'GitRemote' which is depended on by existing Durable Objects. Did you forget to include it? If you renamed it, try a rename-class migration. If you want to delete all the Durable Objects implemented by the class, you can use a delete-class migration [code: 10064]
Metadata
Metadata
Assignees
Labels
Type
Projects
Status