build(deps): bump tokio from 1.42.0 to 1.44.2 in the cargo group

Bumps the cargo group with 1 update: [tokio](https://github.com/tokio-rs/tokio).


Updates `tokio` from 1.42.0 to 1.44.2
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.42.0...tokio-1.44.2)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.44.2
  dependency-type: direct:production
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>

.github/workflows/check.yml

@@ -6,9 +6,6 @@ on:
   merge_group:
     branches:
     - main
-permissions:
-  contents: read
-
 jobs:
   rustfmt:
     name: rustfmt

.github/workflows/release-plz.yml

@@ -6,9 +6,6 @@ on:
 concurrency:
   group: "${{ github.workflow }}"
   cancel-in-progress: true
-permissions:
-  contents: read
-
 jobs:
   release-plz:
     name: release-plz

CHANGELOG.md

@@ -7,12 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.0.25](https://github.com/edera-dev/krata/compare/v0.0.24...v0.0.25) - 2025-07-03
-
-### Other
-
-- update Cargo.toml dependencies
-
 ## [0.0.24](https://github.com/edera-dev/krata/compare/v0.0.23...v0.0.24) - 2024-12-14
 
 ### Added

Cargo.lock

@@ -259,7 +259,7 @@ checksum = "7943c866cc5cd64cbc25b2e01621d07fa8eb2a1a23160ee81ce38704e97b8ecf"
 
 [[package]]
 name = "krata-xencall"
-version = "0.0.25"
+version = "0.0.24"
 dependencies = [
  "env_logger",
  "libc",
@@ -271,7 +271,7 @@ dependencies = [
 
 [[package]]
 name = "krata-xenclient"
-version = "0.0.25"
+version = "0.0.24"
 dependencies = [
  "async-trait",
  "bit-vec",
@@ -289,7 +289,7 @@ dependencies = [
 
 [[package]]
 name = "krata-xenevtchn"
-version = "0.0.25"
+version = "0.0.24"
 dependencies = [
  "byteorder",
  "libc",
@@ -301,7 +301,7 @@ dependencies = [
 
 [[package]]
 name = "krata-xengnt"
-version = "0.0.25"
+version = "0.0.24"
 dependencies = [
  "libc",
  "nix",
@@ -310,7 +310,7 @@ dependencies = [
 
 [[package]]
 name = "krata-xenplatform"
-version = "0.0.25"
+version = "0.0.24"
 dependencies = [
  "async-trait",
  "elf",
@@ -330,7 +330,7 @@ dependencies = [
 
 [[package]]
 name = "krata-xenstore"
-version = "0.0.25"
+version = "0.0.24"
 dependencies = [
  "byteorder",
  "env_logger",
@@ -593,9 +593,9 @@ dependencies = [
 
 [[package]]
 name = "tokio"
-version = "1.42.0"
+version = "1.44.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "5cec9b21b0450273377fc97bd4c33a8acffc8c996c987a7c5b319a0083707551"
+checksum = "e6b88822cbe49de4185e3a4cbf8321dd487cf5fe0c5c65695fef6346371e9c48"
 dependencies = [
  "backtrace",
  "bytes",
@@ -611,9 +611,9 @@ dependencies = [
 
 [[package]]
 name = "tokio-macros"
-version = "2.4.0"
+version = "2.5.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "693d596312e88961bc67d7f1f97af8a70227d9f90c31bba5806eec004978d752"
+checksum = "6e06d43f1345a3bcd39f6a56dbb7dcab2ba47e68e8ac134855e7e2bdbaf8cab8"
 dependencies = [
  "proc-macro2",
  "quote",

Cargo.toml

@@ -10,7 +10,7 @@ members = [
 resolver = "2"
 
 [workspace.package]
-version = "0.0.25"
+version = "0.0.24"
 homepage = "https://krata.dev"
 license = "GPL-2.0-or-later"
 repository = "https://github.com/edera-dev/krata"
@@ -33,7 +33,7 @@ thiserror = "2.0.9"
 xz2 = "0.1"
 
 [workspace.dependencies.tokio]
-version = "1.41.1"
+version = "1.44.2"
 features = ["full"]
 
 [workspace.dependencies.uuid]

README.md

@@ -11,7 +11,6 @@ krata is an implementation of a Xen control-plane in Rust.
 - [Frequently Asked Questions](FAQ.md)
 - [Code of Conduct](CODE_OF_CONDUCT.md)
 - [Security Policy](SECURITY.md)
-- [Edera Technical Overview](technical-overview.md)
 
 ## Introduction
 
@@ -24,4 +23,3 @@ It provides the base layer upon which Edera Protect zones are built on: a secure
 |--------------|------------------|-------------------------|
 | x86_64       | 100% Completed   | None, Intel VT-x, AMD-V |
 | aarch64      | 10% Completed    | AArch64 virtualization  |
-

crates/xen/xenclient/Cargo.toml

@@ -13,9 +13,9 @@ async-trait = { workspace = true }
 bit-vec = { workspace = true }
 indexmap = { workspace = true }
 log = { workspace = true }
-krata-xencall = { path = "../xencall", version = "^0.0.25" }
-krata-xenplatform = { path = "../xenplatform", version = "^0.0.25" }
-krata-xenstore = { path = "../xenstore", version = "^0.0.25" }
+krata-xencall = { path = "../xencall", version = "^0.0.24" }
+krata-xenplatform = { path = "../xenplatform", version = "^0.0.24" }
+krata-xenstore = { path = "../xenstore", version = "^0.0.24" }
 regex = { workspace = true }
 thiserror = { workspace = true }
 tokio = { workspace = true }

crates/xen/xenplatform/Cargo.toml

@@ -14,7 +14,7 @@ elf = { workspace = true }
 flate2 = { workspace = true }
 libc = { workspace = true }
 log = { workspace = true }
-krata-xencall = { path = "../xencall", version = "^0.0.25" }
+krata-xencall = { path = "../xencall", version = "^0.0.24" }
 memchr = { workspace = true }
 nix = { workspace = true }
 regex = { workspace = true }

technical-overview.md

@@ -1,95 +0,0 @@
-# Edera Technical Overview
-
-## What is Edera?
-
-Edera is a secure-by-default, cloud-native platform built on a reimagined, memory-safe type-1 hypervisor. It unlocks hard multitenancy and strong container isolation—without the performance hit.
-
-Unlike traditional container runtimes that share a single Linux kernel across containers, Edera runs each container in a lightweight virtual machine (called a **zone**), with its own dedicated Linux kernel. This eliminates the kernel as a shared attack surface.
-
-And because Edera doesn’t rely on nested virtualization, it runs wherever containers do—across public clouds, on-prem, and edge environments.
-
-## How Edera Works
-
-At its core, Edera uses a [custom hypervisor](https://edera.dev/stories/rust-or-bust-our-rewrite-of-the-xen-control-plane) based on [Xen](https://edera.dev/stories/why-edera-built-on-xen-a-secure-container-foundation), with key components rewritten in Rust for safety, performance, and maintainability. Edera introduces the concept of **zones**—independent, fast-booting virtual machines that serve as security boundaries for container workloads.
-
-Each zone runs its own Linux kernel and minimal init system. The kernel and other system components are delivered via OCI images, keeping things composable, cacheable, and consistent.
-
-Zones are [paravirtualized](https://docs.edera.dev/concepts/paravirtualization/) using the Xen PV protocol. This keeps them lightweight and fast—no hardware virtualization required. But when hardware support is available (e.g., on x86 with VT-x), Edera uses it to get near bare-metal performance.
-
-## How Edera Runs & Secures Containers
-
-Edera allows you to compose your infrastructure the same way you compose workloads: using OCI images.
-
-Each zone consumes a small number of OCI images:
-
-- A **kernel image** that provides the zone kernel.
-- One or more **system extension images** that provide init systems, utilities, and kernel modules.
-- Optionally, **driver zones**—zones that provide shared services (like networking) to other zones.
-
-Inside each zone, container workloads run via a minimal OCI runtime called [**Styrolite**]((https://github.com/edera-dev/styrolite/)), written in Rust. Unlike traditional setups (like Kata Containers, which layer containerd and runc as external processes), Styrolite is embedded inside the zone itself.
-
-### Key Benefits of This Design
-
-- No external container runtime processes  
-- Zone init system directly manages containers  
-- Minimal attack surface, optimized for secure execution
-
-This tightly integrated design avoids the complexity, latency, and exposure introduced by conventional container runtimes. It keeps the execution path short, verifiable, and secure-by-design.
-
-## Zones as Security Boundaries
-
-In Kubernetes, Edera runs pods inside **zones**—isolated virtual machines that eliminate risks like container escape, privilege escalation, and lateral movement.
-
-Each zone boots its own kernel, pulled via OCI, and runs a single pod by default. You can also configure zones to run a replica set, a namespace, or a set of trusted workloads together.
-
-To use Edera, apply the `RuntimeClass`:
-
-```yaml
-apiVersion: node.k8s.io/v1
-kind: RuntimeClass
-metadata:
-  name: edera
-handler: edera
-```
-
-Then annotate your pod:
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: edera-protect-pod
-spec:
-  runtimeClassName: edera
-```
-
-This causes the pod to be scheduled to a node running Edera’s hypervisor. The pod is transparently launched inside its own VM zone—no image changes, no config rewrites, and no extra work from developers.
-
-## What Exactly Is an Edera Zone?
-
-An Edera zone is a minimal VM built from OCI-delivered components. At launch time, the Edera daemon unpacks:
-
-### Kernel Image
-
-Located under `/kernel` in the OCI image:
-
-- `image`: the Linux kernel (vmlinuz)
-- `metadata`: key-value pairs for boot parameters
-- `addons.squashfs`: includes kernel modules in `/modules`
-- `config.gz`: the kernel configuration file
-
-### Initramfs Contents
-
-Packaged in a CPIO archive, typically mounted from:
-`usr/lib/edera/protect/zone/initrd`
-
-The initramfs includes:
-
-- `/init`: static Rust binary that initializes the zone
-- `/bin/styrolite`: embedded container runtime
-- `/bin/zone`: control plane for managing containers and services via IDM (inter-domain messaging)
-
-This structure lets Edera launch zones rapidly, with well-defined boundaries and no dependency on the host OS kernel. Everything the workload touches is defined, versioned, and validated.
-
----
-If you want to know more check out our [docs site](https://docs.edera.dev)