Skip to content

Releases: daytonaio/daytona

v0.22.1

17 Jul 16:56
767755a
Compare
Choose a tag to compare

What's Changed

Fixes

  • fix: code command runtime error on select workspace by @lbrecic in #783

Chores and tests

  • refactor: save build results in database by @lbrecic in #758

Full Changelog: v0.22.0...v0.22.1

v0.22.0

12 Jul 12:21
1a69d94
Compare
Choose a tag to compare

What's Changed

Features

Fixes

Chores and tests

  • chore(deps): bump github.com/google/nftables from 0.1.1-0.20230115205135-9aa6fdf5a28c to 0.2.0 by @dependabot in #741
  • docs: minor update to content and slack fix by @nkkko in #756
  • Point the user to the OSX specific documentation for (install and) add to PATH by @SvenDowideit in #743
  • refactor: passing ssh client to docker client methods by @Tpuljak in #762

Breaking changes

#762

Since the provider interface changed, users will need to update their providers with daytona provider update.

New Contributors

Full Changelog: v0.21.3...v0.22.0

v0.21.3

08 Jul 14:27
ddde265
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.21.2...v0.21.3

v0.21.2

08 Jul 13:42
2613909
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.21.1...v0.21.2

v0.21.1

28 Jun 14:06
c3cf22e
Compare
Choose a tag to compare

What's Changed

  • fix: devcontainer config file name validation by @RS-labhub in #714
  • fix: devcontainer read config environment variables by @Tpuljak in #715

Notes

The change will require providers to be updated with daytona provider update

Full Changelog: v0.21.0...v0.21.1

v0.21.0

28 Jun 10:26
583c0ab
Compare
Choose a tag to compare

Major update

Build projects on the target machine (#708)

A significant refactor is made to how the workspace creation process is run. The process is now ran on the target machine (local or remote) and directly on the host (before the process was ran inside a container). With this change, the creation process will see a significant performance improvement, especially on subsequent builds, because it will be cached on the hosts docker registry. Additionally, devcontainer Docker specific capabilities (e.g. gpu support) are now supported alongside full support for devcontainers that leverage docker compose projects.

What's Changed / Minor updates

Features

Fixes

  • fix: logging improvements by @idagelic in #711
  • fix: Using git providers hosted without HTTPS fails to clone repositories by @RS-labhub in #704

Chores and tests

  • chore(deps): bump github.com/hashicorp/go-retryablehttp from 0.7.2 to 0.7.7 by @dependabot in #709
  • style: gitness vars naming by @idagelic in #707

Breaking changes

#708

The provider interface was changed so they will need to be updated by the user using daytona provider update

New Contributors

Full Changelog: v0.20.0...v0.21.0

v0.21.0-alpha.1

26 Jun 10:21
Compare
Choose a tag to compare
v0.21.0-alpha.1 Pre-release
Pre-release

Major update

Build projects on the target machine (#708)

A significant refactor is made to how the workspace creation process is run. The process is now ran on the target machine (local or remote) and directly on the host (before the process was ran inside a container). With this change, the creation process will see a significant performance improvement, especially on subsequent builds, because it will be cached on the hosts docker registry. Additionally, devcontainer Docker specific capabilities (e.g. gpu support) are now supported alongside full support for devcontainers that leverage docker compose projects.

What's Changed / Minor updates

Features

Fixes

  • fix: logging improvements by @idagelic in #711
  • fix: Using git providers hosted without HTTPS fails to clone repositories by @RS-labhub in #704

Chores and tests

  • chore(deps): bump github.com/hashicorp/go-retryablehttp from 0.7.2 to 0.7.7 by @dependabot in #709

Breaking changes

#708

The provider interface was changed so they will need to be updated by the user using daytona provider update

Notes

To test this prerelease, users will have to configure their server to use the prerelease channel for our providers. To do so, follow these steps:

  1. daytona serve
  2. daytona server configure -> change Registry URL to https://download.daytona.io/daytona-providers-pre-release
  3. daytona provider install -> select v0.7.0-alpha.1
  4. Restart the daytona serve process

New Contributors

Full Changelog: v0.20.0...v0.21.0-alpha.1

v0.20.0

21 Jun 11:17
96c2e75
Compare
Choose a tag to compare

What's Changed

Features

Breaking changes

#683

Because of changes to our logging package, users will have to update their providers with daytona provider update

New Contributors

Full Changelog: v0.19.1...v0.20.0

v0.19.1

17 Jun 09:51
1233508
Compare
Choose a tag to compare

What's Changed

Fixes

Full Changelog: v0.19.0...v0.19.1

v0.19.0

14 Jun 16:02
89d96c5
Compare
Choose a tag to compare

What's Changed

Features

Fixes

  • fix: custom image builder select by @Tpuljak in #677
  • fix: workspace create fails when repo/project have spaces by @tarunrajput in #630
  • fix: improve workspace creation summary view by @lbrecic in #680

Chores and tests

Breaking changes

#660

Before starting the server, users will need to add 'localBuilderRegistryPort' and 'builderRegistryServer' properties to their server configuration.
The following properties should be added:

  "localBuilderRegistryPort": 3988,
  "builderRegistryServer": "local",

(Note: "registryPort" can be removed from the config file)

On Mac
The file is located at: ~/Library/Application\ Support/daytona/server/config.json.

On Linux
The file is located at: ~/.config/daytona/server/config.json

On Windows
The file is located at: C:\Users\YOUR_USERNAME\AppData\Roaming\daytona\server\config.json

#667

With #667, the provider initialization method was changed which requires all providers to be updated with daytona provider update.

Full Changelog: v0.18.0...v0.19.0