From 372b911b58892e5517c007a1b617390daa03e687 Mon Sep 17 00:00:00 2001 From: Jakub Novak Date: Wed, 29 Jul 2026 08:38:08 +0000 Subject: [PATCH] feat(release): deploy kernels to Tango --- .github/workflows/release.yml | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 384d1f7..efe3197 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -153,7 +153,7 @@ jobs: strategy: fail-fast: false matrix: - environment: [staging, juliett, foxtrot] + environment: [staging, juliett, foxtrot, tango] runs-on: ubuntu-24.04 environment: ${{ matrix.environment }} permissions: diff --git a/README.md b/README.md index 4fb2529..706c6df 100644 --- a/README.md +++ b/README.md @@ -40,7 +40,7 @@ Release asset naming for that commit: vmlinux-.bin # legacy (= amd64) for backwards compat ``` -4. The arch-specific binaries are uploaded to each deploy environment's GCS bucket at `gs://$GCP_BUCKET_NAME/kernels/vmlinux-_//vmlinux.bin`. Deploy environments: `staging`, `juliett`, `foxtrot`. To upload an existing release to a bucket manually, run `./scripts/upload-release-to-gcs.sh --hash --bucket /kernels` (add `--dry-run` to preview). Existing objects are never overwritten. +4. The arch-specific binaries are uploaded to each deploy environment's GCS bucket at `gs://$GCP_BUCKET_NAME/kernels/vmlinux-_//vmlinux.bin`. Deploy environments: `staging`, `juliett`, `foxtrot`, `tango`. To upload an existing release to a bucket manually, run `./scripts/upload-release-to-gcs.sh --hash --bucket /kernels` (add `--dry-run` to preview). Existing objects are never overwritten. ## New kernel in E2B's infra _Note: these steps should give you a new kernel on your self-hosted E2B using https://github.com/e2b-dev/infra_