You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Targets now have state (e.g. Daytona is aware of the state of the EC2 instance used by the AWS provider)
Workspaces can be created/deleted on running targets (e.g. No more need to create an EC2 instance for every workspace. Keep one running and add workspaces to it)
Remote runners can offload jobs to remote machines
Use workspace labels to group workspaces and filter them with daytona ls --label
If you want to help us test this major update, jump straight into the How to test section below
Description
Projects have been renamed to Workspaces.
Workspaces have been renamed to Targets
Targets have been renamed to Target Configs.
Project configs have also been renamed to Templates; e.g. daytona template list
Workspaces have been "detached" from targets - they can now be created inside and deleted from targets removing the
need to provision a new target whenever creating a workspace.
Resource state management issues have been resolved - new resource states regarding starting/stopping/deleting workspaces or e.g. running builds are introduced.
Issues for a "remote provisioner" and "remote image builder" have been solved by introducing Runners - a standalone mode/component in charge of asynchronously fetching and running workspace/target/build creation and other processes.
This allows users to e.g. create a remote VM, install Daytona and connect it to the existing Daytona Server to create workspaces. Local provisioning/building is managed by the Local Runner which can be disabled through the Daytona
Server configuration.
Runners are responsible for managing providers and each one has its own set of providers. When creating target configs, users are prompted to choose a runner to link it to.
If you want to add a remote runners, run:
daytona server runner create
You will get a command that you can run to configure and start a remote runner.
Introduced Workspace Labels allowing workspaces to be grouped and filtered by user-defined text fields.
It is now possible to SSH into targets and use the Daytona binary inside of them to view info and read logs.
Container registries are no longer managed through a CLI command and are now managed by environment variables instead
Purging Daytona now delegates removal of Resources (workspaces, targets, builds) to the user because they are now treated independently.
Telemetry has been updated/improved to match the changes.
CLI commands arguments and aliases have been made to be more consistent.
README.md has been redone to adhere to the changes and trimmed of a large amount of the content.
Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.
Affected range
>=1.23.0-0 <1.23.1
Fixed version
1.23.1
Description
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
Affected range
>=1.23.0-0 <1.23.1
Fixed version
1.23.1
Description
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
Affected range
>=1.23.0-0 <1.23.1
Fixed version
1.23.1
Description
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.
github.com/aws/aws-sdk-go1.54.19 (golang)
pkg:golang/github.com/aws/aws-sdk-go@1.54.19
Affected range
>=0
Fixed version
Not Fixed
Description
A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.
Affected range
>=0
Fixed version
Not Fixed
Description
A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.51.0->0.52.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
daytonaio/daytona (daytonaio/daytona)
v0.52.0Compare Source
Workspace Management Rework
TL;DR
daytona ls --labelHow to test sectionbelowDescription
Projects have been renamed to Workspaces.
Workspaces have been renamed to Targets
Targets have been renamed to Target Configs.
Project configs have also been renamed to Templates; e.g.
daytona template listWorkspaces have been "detached" from targets - they can now be created inside and deleted from targets removing the
need to provision a new target whenever creating a workspace.
Resource state management issues have been resolved - new resource states regarding starting/stopping/deleting workspaces or e.g. running builds are introduced.
Issues for a "remote provisioner" and "remote image builder" have been solved by introducing Runners - a standalone mode/component in charge of asynchronously fetching and running workspace/target/build creation and other processes.
This allows users to e.g. create a remote VM, install Daytona and connect it to the existing Daytona Server to create workspaces. Local provisioning/building is managed by the Local Runner which can be disabled through the Daytona
Server configuration.
Runners are responsible for managing providers and each one has its own set of providers. When creating target configs, users are prompted to choose a runner to link it to.
If you want to add a remote runners, run:
You will get a command that you can run to configure and start a remote runner.
Introduced Workspace Labels allowing workspaces to be grouped and filtered by user-defined text fields.
It is now possible to SSH into targets and use the Daytona binary inside of them to view info and read logs.
Container registries are no longer managed through a CLI command and are now managed by environment variables instead
Purging Daytona now delegates removal of Resources (workspaces, targets, builds) to the user because they are now treated independently.
Telemetry has been updated/improved to match the changes.
CLI commands arguments and aliases have been made to be more consistent.
README.md has been redone to adhere to the changes and trimmed of a large amount of the content.
Other release changes
Features
Fixes
Telemetry
Samples
Chores and tests
Breaking changes
Before updating, users will need to remove the entire Daytona configuration from your system with
daytona purgeor:Linux:
rm -rf ~/.config/daytonaMac:
Windows (PowerShell):
Remove-Item -Recurse -Force "C:\Users\<USERNAME>\AppData\Roaming\daytona"Full Changelog: daytonaio/daytona@v0.51.0...v0.52.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.