0.19.29

Fleets

Over the last few releases, we’ve been reworking how fleets work to radically simplify management and make it fully declarative.

Previously, you had to specify a fleet via fleets explicitly — otherwise, dstack always created a new one. Now, dstack automatically picks an existing fleet if it fits the requirements, creating a new one only when needed.

For more on the fleet roadmap, see this meta issue.

User Interface

Grouping offers by backend

The Offers page in the UI now lets you group available offers by backend, making it easier to compare options across cloud providers.

Breaking changes

• The tensordock backend hasn’t worked for a long time (due to the API it relied on being deprecated) and has now been removed.

What's changed

• [Blog] The state of cloud GPUs in 2025: costs, performance, playbooks by @peterschmidt85 in #3089
• [Docs] Add .dstack/profiles.yml to Reference and Protips by @peterschmidt85 in #3093
• [TensorDock] Remove the tensordock from supported backends #3092 by @peterschmidt85 in #3094
• Unassign scheduled run from fleet on resubmission by @r4victor in #3096
• [UI] Allow to group offers by backend by @olgenn in #3098
• Implement requirements-independent offers cache by @r4victor in #3091
• [Internal] Project config support by @peterschmidt85 in #3097
• Fix long sqlite write transaction when provisioning instances by @r4victor in #3104
• Consider backend offers when choosing optimal fleet by @r4victor in #3101
• [UI] Project wizard by @olgenn in #3103
• Use Cuda 12.0 image for DataCrunch A6000 by @r4victor in #3105
• [UI] Project wizard #323 by @olgenn in #3107

Full changelog: 0.19.28...0.19.29