v0.24.0
What's Changed
Features
- feat: implement get url from repository API route by @Tpuljak in #872
- feat: add workspace status check to code and ssh commands #821 by @titanventura in #822
- feat: aws codecommit git provider by @the-johnwick in #797
- feat: project configs by @idagelic in #789
Fixes
- fix: dont throw a error on ctrl-c for command (#615) by @abhishek818 in #800
- fix: inform user if vscode ide is not installed locally (#654) by @abhishek818 in #868
- fix: add loginctl note for linux server daemon by @Tpuljak in #869
- fix: handle the error message for incorrect token by @harkiratsm in #874
- fix: add a root user check on serve by @Tpuljak in #864
- fix: devcontainer localEnv override by @Tpuljak in #879
- fix: authenticate the providerConfig before adding it DB by @harkiratsm in #878
- fix: gitprovider for url interface by @idagelic in #888
Chores and tests
- chore: server yesFlag description by @idagelic in #875
- chore: swagger version update to 0.24.0 by @idagelic in #889
- chore(deps): bump github.com/docker/docker from 26.0.2+incompatible to 26.1.4+incompatible by @dependabot in #870
- docs: add README to the docker pkg by @Tpuljak in #871
- Remove duplicate repo validation by @abhishek818 in #791
Project Configs
This release introduces a major feature/change: Project Configs - entities that contain all the information necessary to create a new project.
They are managed using the daytona project-config command and allow users to define project configurations in advance and use them when creating workspaces in the future. They contain the relevant repository and build information, environment variables which are then used by default whenever a project with the specified repository is created.
The user gets notified whenever an existing project config is detected, but still has the ability to pass a --blank flag and avoid any preconfigured properties.
Project Configs are part of a bigger effort to incorporate "prebuilds" which will let users set up "ready-to-go" builds and spend less time waiting for their development environments to be ready.
Breaking changes
#789
Since the provider interface changed, users will need to update their providers with daytona provider update.
If used as a library, multiple component/property/package renaming might lead to issues in importing.
New Contributors
- @titanventura made their first contribution in #822
- @the-johnwick made their first contribution in #797
Full Changelog: v0.23.1...v0.24.0
