Skip to content

Releases: daytonaio/daytona

v0.29.0

06 Sep 15:34
4edbf6f
Compare
Choose a tag to compare

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

04 Sep 17:06
674e5d7
Compare
Choose a tag to compare

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

03 Sep 14:45
1d15289
Compare
Choose a tag to compare

What's Changed

Features

Fixes

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

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

v0.27.0

30 Aug 16:01
f798551
Compare
Choose a tag to compare

What's Changed

Features

Fixes

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!

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:

New Contributors

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

v0.26.1

28 Aug 15:33
a839cf7
Compare
Choose a tag to compare

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

27 Aug 16:08
Compare
Choose a tag to compare

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

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.

image

image

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

image

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

image

image

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.

image

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

23 Aug 16:02
Compare
Choose a tag to compare
v0.26.0-alpha.1 Pre-release
Pre-release

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.

image

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

image

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.

image

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.

image

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

v0.25.2

23 Aug 15:11
c1332a8
Compare
Choose a tag to compare

What's Changed

Fixes

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!

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:

Full Changelog: v0.25.1...v0.25.2

v0.25.1

14 Aug 11:29
2c72faa
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.25.0...v0.25.1

v0.25.0

13 Aug 10:55
cd21e05
Compare
Choose a tag to compare

What's Changed

Features

Fixes

  • fix: allow users to submit the form earlier by @harkiratsm in #856
  • fix: change url for repo API response object by @Tpuljak in #900
  • fix: check registry port after removal by @lbrecic in #901
  • fix: add check for Docker requirements in Local Container Registry Start by @tarunrajput in #902
  • fix: server configuration fails to make directory by @tarunrajput in #908
  • fix: remove fatal on project config select ctrl-c by @idagelic in #899
  • fix: daytona creation logs in daytona by @Tpuljak in #898
  • fix: server start fails if systemd file exists by @lbrecic in #903
  • fix: resolve websocket log-reader todos by @lbrecic in #916
  • fix: proper API JSON validation by @Tpuljak in #905

Chores and tests

Breaking changes

#905

The breaking change is regarding to services that rely on our Swagger files and any tools that generate api clients from the definition.

New Contributors

Full Changelog: v0.24.0...v0.25.0