Releases: daytonaio/daytona
v0.3.0
What's Changed
- Check that the DESTINATION dir exists. by @metcalfc in #143
- chore: add fabjanvucina to contributors by @fabjanvucina in #141
- chore: add tarunrajput to contributors by @tarunrajput in #142
- Improve info command by @ezhil56x in #123
- feat: add TARGET column to daytona list by @tarunrajput in #140
- chore: add guptadeepak8 to contributors by @guptadeepak8 in #144
- chore: add vineeth-vk11 to contributors by @vineeth-vk11 in #149
- chore: add 35C4n0r to contributors by @35C4n0r in #150
- chore: update logo in README.md by @fabjanvucina in #151
- fix: skip repo url on single project workspace creation by @tarunrajput in #157
- feat: added all flag by @guptadeepak8 in #118
- delete workspace logs dir on deleting workspace by @vineeth-vk11 in #147
- fix: uname length judgment by @Twacqwq in #153
- chore: add Twacqwq to contributors by @Twacqwq in #160
- feat: auto inject completions by @35C4n0r in #139
- chore: update Go to 1.22.1 by @Tpuljak in #161
- feat: add Branch to list command by @ezhil56x in #154
- Provider update by @Tpuljak in #166
- fix: prevent downloading of already present providers by @Tpuljak in #165
- feat: check for provider updates on server start by @Tpuljak in #167
- fix: single project create by @idagelic in #169
- chore: add .exe to windows providers in manifest by @Tpuljak in #171
- feat: add missing json/yaml outputs by @idagelic in #172
- GitLab self managed by @idagelic in #170
- chore: enable to set binary install path by @zzorica in #176
- chore: add cleanup gha for inactive issues and PRs by @zzorica in #191
- feat: support opening projects in JetBrains IDEs by @Tpuljak in #186
New Contributors
- @fabjanvucina made their first contribution in #141
- @tarunrajput made their first contribution in #142
- @guptadeepak8 made their first contribution in #144
- @vineeth-vk11 made their first contribution in #149
- @35C4n0r made their first contribution in #150
- @Twacqwq made their first contribution in #153
- @zzorica made their first contribution in #176
Full Changelog: v0.2.0...v0.3.0
Contributors
Assets 2
v0.2.0
What's Changed
- Workspace ID as UUID by @Tpuljak in #106
- Update CONTRIBUTORS.md by @idagelic in #117
- Algora badges by @Tpuljak in #115
- Reworking the get-server.sh to install as non root. by @metcalfc in #105
- chore: add vedranjukic to contributors by @vedranjukic in #126
- chore: add neo773 to contributors by @neo773 in #125
- fix: uninstall existing provider before installing by @Tpuljak in #127
- feat: Project selection prompt by @neo773 in #120
- fix: remove legacy whoami info by @idagelic in #128
- chore: add ezhil56x to contributors by @ezhil56x in #130
- fix: kill orphaned provider processes on server start by @Tpuljak in #136
New Contributors
- @metcalfc made their first contribution in #105
- @neo773 made their first contribution in #125
- @ezhil56x made their first contribution in #130
Full Changelog: v0.1.0...v0.2.0
Contributors
Assets 2
0.1.0
Daytona v0.1.0 (Alpha Release)
We are excited to announce the first alpha release of Daytona – the open-source Development Environment Manager that simplifies the setup and management of software development environments.
What's New
This alpha release marks a significant milestone for the Daytona project. It is the culmination of years of experience, innovation, and hard work.
Highlights of v0.1.0:
- Single Binary Setup: A streamlined experience that allows developers to get their environments up and running with a single executable.
- Infrastructure Agnostic: Whether you're working locally or on the cloud, Daytona adapts to your preferred setup.
- Open Source: Dive into the codebase, contribute, and join us in building a tool that fuels developer productivity.
Get Started
To begin using Daytona, run:
sh -c "$(curl -fsSL https://download.daytona.io/daytona/get-server.sh)"Feedback and Contributions
This being an alpha release, we expect there to be bugs and rough edges. We encourage you to open an issue on GitHub with your feedback, which is invaluable to us.
If you're interested in contributing to Daytona, please check out our contributing guidelines and join our community.
We are grateful for your support and enthusiasm as we take this important step toward simplifying the lives of developers everywhere.
Thank you for being a part of the Daytona journey!
Daytona Team