v0.30.1

What's Changed

• fix: install code extensions on create by @Tpuljak in #1088

Full Changelog: v0.30.0...v0.30.1

v0.30.0

What's Changed

Features

• feat(ide): add Jupyter Notebook as IDE option by @onyedikachi-david in #1033
• feat: attempt direct binary download on project create by @Tpuljak in #1080
• feat: Add support for Bitbucket Webhook events by @unsuman in #1048

Fixes

• fix: detect correct user when opening jetbrains IDEs by @Tpuljak in #1081
• fix: bitbucket get repo prs by @idagelic in #1082
• fix: alt screens by @idagelic in #1085

Chores and tests

• chore(deps): upgrade github.com/charmbracelet/huh from v0.2.3 to v0.3.0 by @jemiluv8 in #799

Breaking changes

#1033

Changed the --auto-start flag in code and start to --yes/-y.

Provider updates

#1080

This change will improve creation times of remote and devcontainer workspaces by up to 50%.
No need to update providers if they are already on their latest version.

New Contributors

• @jemiluv8 made their first contribution in #799
• @onyedikachi-david made their first contribution in #1033

Full Changelog: v0.29.1...v0.30.0

v0.29.1

What's Changed

• fix: Handling and Logging of Missing Project Config on Repository Creation (#933) by @bryans-go in #1076
• fix: multi ws select marking by @idagelic in #1078
• fix: add verbose arg to get ws info by @lbrecic in #1077

Provider Updates

The DigitalOcean Provider received two patches that address stopping and destroying workspaces. Please update to v0.1.5 using daytona provider update.

New Contributors

• @bryans-go made their first contribution in #1076

Full Changelog: v0.29.0...v0.29.1

v0.29.0

What's Changed

Features

• feat: add a workspace start prompt in daytona code for stopped projects by @tarunrajput in #991

Fixes

• fix: bitbucket default branch setting by @lbrecic in #1057
• fix: use open instead of stat to check permissions by @Tpuljak in #1065
• fix: move include daytona config to first line by @lbrecic in #1063
• fix: remove obsolete provider flag from create command by @Tpuljak in #1066
• fix: remove duplicate image pulling on project create by @lbrecic in #1067
• fix: fetch branches with correct options provided from bitbucket by @lbrecic in #1068
• fix: add timeout to get workspace info from provider by @idagelic in #1058

Chores and tests

• telemetry: track IDE id by @Tpuljak in #1064
  • We added a property called ide to telemetry events related to opening a project and daytona ide. The value of the property is the ID of the IDE used.

Provider Updates

#1067 influences all of our providers which, existing users, will need to update with daytona provider update if they want the quickest project creation time.

Docker Provider => v0.10.2
AWS Provider => v0.1.2
DigitalOcean Provider => v0.1.3

Full Changelog: v0.28.1...v0.29.0

v0.28.1

What's Changed

• refactor: remove owner param from get commits range by @idagelic in #1050
• fix: update headscale to v0.23.0-beta3 by @Tpuljak in #1053

Provider Updates

#1053 influences both the DigitalOcean and AWS provider which, existing users, will need to update with daytona provider update.

Full Changelog: v0.28.0...v0.28.1

v0.28.0

What's Changed

Features

• feat: Support for Webhook events for GitLab/GitLab self-managed prebuilds by @unsuman in #1026
• feat: uninteractive project config creation by @idagelic in #1000
• feat: add provider prefix option to logs by @idagelic in #1045
• feat: add code flag to daytona start cmd by @tarunrajput in #1004
• feat: direct ssh access to local workspaces by @Tpuljak in #1040
• feat: install provider during target set by @idagelic in #1043

Fixes

• fix: pc add image user nil check by @idagelic in #1038
• fix: fetch image user from project config on create by @idagelic in #1039
• fix: windows style carriage returns by @idagelic in #1020
• fix: choose git provider label by @idagelic in #1046
• fix: consider env variable while running daytona server start by @aman23bedi in #1041
• fix: ws select sort by @idagelic in #1021
• fix: check binary permissions before serving by @Tpuljak in #1047

Provider Updates

Docker Provider

https://github.com/daytonaio/daytona-provider-docker/releases/tag/v0.10.1

• This release includes a big improvement for download speeds for local non-devcontainer workspaces.

You can update to the latest provider release with daytona provider update.

New Contributors

• @unsuman made their first contribution in #1026
• @aman23bedi made their first contribution in #1041

Full Changelog: v0.27.0...v0.28.0

v0.27.0

What's Changed

Features

• feat: add Create from Sample creation option by @Tpuljak in #954
• feat: update headscale to 0.23.0-beta2 by @Tpuljak in #1010
• feat: add -v flag to root cmds by @idagelic in #1019
• feat: add custom installation loader to the install script by @varshith257 in #983

Fixes

• fix: update profile name validation to match workspace name by @tarunrajput in #987
• fix: refactored output flag to accomodate selection tui by @joey1123455 in #1009
• fix: opening cursor instead of vscode by @Tpuljak in #973
• fix(gitlab): Configure SHA property for static git context by @mobley-trent in #1003
• fix: update list of supported ides in daytona code and create by @tarunrajput in #1008
• fix: handle logging build deletion errors by @idagelic in #992
• fix: log read cancellation by @Tpuljak in #1005

Chores and tests

• chore(deps): bump google.golang.org/grpc from 1.64.0 to 1.64.1 by @dependabot in #1015

Breaking changes

#1009

The --output/-o flag was renamed to --format/-f.

Notes

#954

To use Samples, users can run daytona server configure and add https://raw.githubusercontent.com/daytonaio/daytona/main/hack/samples/index.json to the Samples Index Url property.
After restarting the server and running daytona create, you should be able to select a sample to quickly get started in a popular tech stack.

New Providers

We have released 2 new providers!

• AWS Provider that creates an EC2 instance for you to work in
• DigitalOcean Provider that creates a DigitalOcean Droplet for you to work in

To install these providers, users can run: daytona provider install

You can find more info about them on our docs page (https://www.daytona.io/docs/configuration/providers/#officially-supported-providers)

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

New Contributors

• @varshith257 made their first contribution in #983

Full Changelog: v0.26.1...v0.27.0

v0.26.1

What's Changed

Fixes

• fix: improve error handling for daytona code command by @Divanshu-Grover in #948
• fix: error wrapping %w used for error instead of %s by @Divanshu-Grover in #959
• fix: timestamp with timezone by @idagelic in #981
• fix: run prompt on prebuild add/update by @idagelic in #984
• fix: add project config during prebuilds add flow by @idagelic in #978
• fix: register env var deletion by @lbrecic in #980
• fix: matching project config and build to repository by @Tpuljak in #976
• fix: build logs UX by @idagelic in #975

Full Changelog: v0.26.0...v0.26.1

v0.26.0

What's Changed

Features

• feat: flag for the project-config delete command to delete all project configurations by @Divanshu-Grover in #949
• feat: cursor IDE support by @Tpuljak in #960
• feat: prebuilds by @idagelic in #912 - read more about prebuilds below

Fixes

• fix: clone project from commit url by @the-johnwick in #873
• fix: commit clone infinite loop by @idagelic in #964
• fix: handle api errors that return html by @Tpuljak in #952

Chores and tests

• chore: mark git directory as safe in devcontainer by @Tpuljak in #951

Prebuilds

This release introduces prebuilds - a way to speed up development by setting a project configuration to listen to changes in the underlying repository and run a build whenever it is necessary to ensure that once the user wants to create a project and start working, the creation process is much quicker.
Using daytona prebuilds add opens a view that lets asks the user to select a project configuration and the Git branch they plan to work on. The user can then decide on a commit interval after which a build should be triggered as well as any specific trigger files whose changes should immediately start the build process.

Consequent daytona create calls will automatically detect the most recent existing build and use it to create the project much faster.

daytona build list and daytona build logs allow the user to view the builds and their information or debug the process. daytona build rm --all lets the user delete the builds to clear up space.
daytona build logs [BUILD_ID] -f lets the user view the build progress

The prebuilds work by registering a listener to webhook event from the Git provider by sending a public API endpoint that the Git provider will send requests to. Currently only GitHub is supported, but more options are coming soon.

Breaking changes

• Due to changes in interfaces, existing project configs will need to be re-added.
• Providers will need to be updated with daytona provider update
• GetGitContext is now a POST request that takes a GetRepositoryContext object instead of GET request that takes a repository URL
• To resolve database migration issues:

a) If you don't mind losing existing workspaces and configuration, you can simply delete the Daytona config directory

On Mac - rm -rf ~/Library/Application\ Support/daytona
On Linux - rm -rf ~/.config/daytona
On Windows - rmdir C:\Users\YOUR_USERNAME\AppData\Roaming\daytona

b) To keep the current configuration, it is necessary to run this SQL command: DROP TABLE IF EXISTS build_dtos; after stopping the Daytona server and before starting it up again. To do this you need to first install the SQLite CLI by following the steps available on SQLite.org and then run the following commands:

sqlite3 [DAYTONA_CONFIG_DIR]/db
DROP TABLE IF EXISTS build_dtos;

If using Windows make sure to call the correct executable file - sqlite3.exe instead of sqlite3

New Contributors

• @Divanshu-Grover made their first contribution in #949

Full Changelog: v0.25.2...v0.26.0

v0.26.0-alpha.1

Prebuilds

This release introduces prebuilds - a way to speed up development by setting a project configuration to listen to changes in the underlying repository and run a build whenever it is necessary to ensure that once the user wants to create a project and start working, the creation process is much quicker.
Using daytona prebuilds add opens a view that lets asks the user to select a project configuration and the Git branch they plan to work on. The user can then decide on a commit interval after which a build should be triggered as well as any specific trigger files whose changes should immediately start the build process.

NOTE: GitHub is currently the only git provider that supports prebuilds.

Consequent daytona create calls will automatically detect the most recent existing build and use it to create the project much faster.

daytona build list and daytona build logs allow the user to view the builds and their information or debug the process. daytona build rm --all lets the user delete the builds to clear up space.

The prebuilds work by registering a listener to webhook event from the Git provider by sending a public API endpoint that the Git provider will send requests to. Currently only GitHub is supported, but more options are coming soon.

Breaking changes

• Due to changes in interfaces, existing project configs will need to be re-added (daytona pc rm && daytona pc add).
• To resolve database migration issues it is necessary to run this SQL command: DROP TABLE IF EXISTS build_dtos; after stopping the Daytona server and before starting it up again. To do this you need to first install the SQLite CLI by following the steps available on SQLite.org and then run the following commands:

On Mac
sqlite3 ~/Library/Application\ Support/daytona/server/db
DROP TABLE IF EXISTS build_dtos;

On Linux
sqlite3 ~/.config/daytona/server/db
DROP TABLE IF EXISTS build_dtos;

On Windows
sqlite3.exe C:\Users\YOUR_USERNAME\AppData\Roaming\daytona\server\db
DROP TABLE IF EXISTS build_dtos;

Note

To test this release, users will have to configure their server to use the prerelease channel for our providers and install version v0.10.0-alpha.1 of the Docker Provider (other providers are currently not supported). 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 -> install the Docker Provider version v0.10.0-alpha.1

Installation

To install this pre-release, run curl -sf -L https://download.daytona.io/daytona/install.sh | DAYTONA_SERVER_VERSION=v0.26.0-alpha.1 sudo -E bash

Full Changelog: v0.25.2...v0.26.0-alpha.1