Releases: daytonaio/daytona
v0.21.2
What's Changed
- fix: sudo dockerd removed by @RS-labhub in #717
- chore(deps): bump github.com/gin-contrib/cors from 1.5.0 to 1.6.0 by @dependabot in #730
Full Changelog: v0.21.1...v0.21.2
Contributors
Assets 2
v0.21.1
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
Contributors
Assets 2
v0.21.0
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
- feat: add azure devops git provider by @tarunrajput in #610
- feat: allow user to override workspace image at creation by @lbrecic in #691
- feature: add self hosting support for bitbucket by @abhishek818 in #606
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
- @RS-labhub made their first contribution in #704
Full Changelog: v0.20.0...v0.21.0
Contributors
Assets 2
v0.21.0-alpha.1
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
- feat: add azure devops git provider by @tarunrajput in #610
- feat: allow user to override workspace image at creation by @lbrecic in #691
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:
daytona servedaytona server configure-> change Registry URL to https://download.daytona.io/daytona-providers-pre-releasedaytona provider install-> selectv0.7.0-alpha.1- Restart the
daytona serveprocess
New Contributors
- @RS-labhub made their first contribution in #704
Full Changelog: v0.20.0...v0.21.0-alpha.1
Contributors
Assets 2
v0.20.0
What's Changed
Features
- feat: expose server CLI version by @lbrecic in #693
- feat: add gitness provider by @Rutik7066 in #689
- feat: logging improvements by @idagelic in #683
Breaking changes
#683
Because of changes to our logging package, users will have to update their providers with daytona provider update
New Contributors
- @Rutik7066 made their first contribution in #689
Full Changelog: v0.19.1...v0.20.0
Contributors
Assets 2
v0.19.1
v0.19.0
What's Changed
Features
- feat: custom builder registry configuration by @Tpuljak in #660
- feat: Force workspace removal by @mobley-trent in #656
- feat: read server logs while starting as daemon by @Tpuljak in #674
- feat: direct api and headscale access by @Tpuljak in #667
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
Contributors
Assets 2
v0.18.0
What's Changed
Features
- feat: builder image configuration by @Tpuljak in #642
- feat: add daytona docs command by @lbrecic in #637
- feat: generate yaml docs by @idagelic in #641
- feat: ability to delete multiple workspaces. Issue #378 by @shashank40 in #636
Fixes
- fix: Improve provider install UI by @lbrecic in #629
- fix 'profile rm' command, #645 by @abhishek818 in #653
- fix: stop server before upgrading by @ezhil56x in #639
- fix: builder image default value by @Tpuljak in #659
- fix: hide registry password from API response by @Tpuljak in #661
Chores and tests
Breaking changes
Users will need to run daytona server configure, set the Builder Image to daytonaio/workspace-project:latest and restart the server before creating new workspaces. This change is causes by #642
New Contributors
- @abhishek818 made their first contribution in #653
- @shashank40 made their first contribution in #636
Full Changelog: v0.17.0...v0.18.0
Contributors
Assets 2
v0.17.0
Major update
Project Builders (#363)
Projects will now be built using one of the available builders. The first one available is the DevContainer builder.
User are able to choose how their project will be built in the advanced configuration view, or leave it up to Daytona to automatically detect the used configuration standard of a project.
What's Changed / Minor updates
Features
- feat: git provider required scopes by @idagelic in #583
- feat: ask user to remove workspaces when removing target by @mobley-trent in #599
- feat: mount volume to project container by @Tpuljak in #585
- feat: cli docs generation command by @idagelic in #609
Fixes
- fix: multi-project create not working by @tarunrajput in #578
- fix: store project and workspace api keys in db by @Tpuljak in #591
- fix: gp delete view by @idagelic in #584
- fix: project order number by @idagelic in #597
- fix: server daemon fails by @idagelic in #604
- fix: disable docs auto gen tag by @idagelic in #624
Chores and tests
- chore: workspace-project image fixes by @Tpuljak in #623
- docs: update Slack link by @Tpuljak in #608
- refactor: apiclient package name by @idagelic in #573
Breaking changes
Users should run daytona server configure and edit the Build Registry Port to 3988. After the change was made, users need to restart the server.
New Contributors
- @mobley-trent made their first contribution in #599
Full Changelog: v0.16.0...v0.17.0
Contributors
Assets 2
v0.17.0-alpha.4
- creation log and agent command log fixes
Full Changelog: v0.17.0-alpha.3...v0.17.0-alpha.4