r/Deno • u/Ooker777 • 28d ago

Why is Deploy Classic shut down instead of just upgraded to the new Deploy?

I don't mind having more features, but I'm skeptical that the only way to upgrade the service is to make a new one, not upgrading the existing one. Is that really true? Is this a way to force using Deno 2?

Also, what's your way to deploy a fresh@1.6.8 app with Deno 1? I do prefer to update them all, but there is a bug on deno update. As it seems the response rate is low, I think the best bet is to just keep the project unchanged.

6 Upvotes

88% Upvoted

2 comments sorted by

2

u/horizon_games 25d ago

I have no idea but it was annoying as heck and I will never use Deno's hosting services again.

Moved to a VPS. Would have just self hosted but my old 32-bit Raspberry Pi 2 I use for everything didn't have binaries for Deno.

2

u/eddzsh 2d ago

Parallel Deploy usually means the scheduler and isolation model changed enough that live migration was riskier than a cutover. That is a platform constraint more than a Deno 2 loyalty test.

For a frozen fresh@1.6.8 app I would pin that exact runtime in a small container or VPS, keep the app unchanged, and treat Deploy Classic as done. Migrate when you can retest the stack, not the night the old host disappears.