What's Changed
Fixes
- fix: lint errors by @Tpuljak in #922
- fix: devcontainer read config race condition by @Tpuljak in #927
- fix: version mismatch warning displays wrong versions by @RS-labhub in #941
- fix: save stopped workspace if telemetry is disabled by @Tpuljak in #918
- fix: home folder when installing vscode extensions by @Tpuljak in #931
- fix: .devcontainer.json detection by @Tpuljak in #943
- fix: handle binary download interruptions by @Tpuljak in #942
- fix: remove log retry by @lbrecic in #945
Chores and tests
- chore: add dev env variables to vscode launch configs by @Tpuljak in #930
- docs: add packaging guidelines by @Tpuljak in #923
Notes
Because of #927 and #943, providers will need to be updated with daytona provider update (this refers only to the Docker Provider currently).
New Providers
We have 3 new providers with an alpha release!
- AWS Provider that creates an EC2 instance for you to work in
- DigitalOcean Provider that creates a DigitalOcean Droplet for you to work in
- Fly.io Provider that creates a fly.io machine for you to work in
To test the alpha versions of these providers, users will have to configure their server to use the prerelease channel for our providers. To do so, follow these steps:
daytona serve
daytona server configure -> change Registry URL to https://download.daytona.io/daytona-providers-pre-release
daytona provider install -> select the provider you wish to install
daytona target set -> add a new target to the installed provider
If any issues occur with the providers, we kindly ask you to submit the issue in the appropriate repository:
- https://github.com/daytonaio/daytona-provider-aws
- https://github.com/daytonaio/daytona-provider-digitalocean
- https://github.com/daytonaio/daytona-provider-fly
Full Changelog: v0.25.1...v0.25.2