[PR #4] [MERGED] Track latest E2B clients in compatibility tests #116

New issue

Closed

opened 2026-10-29 14:19:52 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-29 14:19:52 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/4
Author: @LSX-s-Software
Created: 7/26/2026
Status: ✅ Merged
Merged: 7/27/2026
Merged by: @yingdi-shan

Base: main ← Head: test/e2b

📝 Commits (1)

cd32e5a test: track latest E2B clients in compatibility tests

📊 Changes

8 files changed (+13 additions, -951 deletions)

View changed files

📝 .github/workflows/integration-tests.yml (+6 -4)
📝 docs/src/configuration/env-vars.md (+2 -2)
📝 docs/src/integration/e2b-cli.md (+1 -1)
📝 docs/src/integration/e2b-sdk.md (+1 -1)
➖ scripts/tests/e2e/package-lock.json (+0 -937)
📝 scripts/tests/e2e/package.json (+0 -3)
📝 scripts/tests/e2e/suites/09_e2b_compat.sh (+2 -2)
📝 scripts/tests/e2e/suites/14_code_interpreter.sh (+1 -1)

📄 Description

Summary

install the latest stable E2B CLI, Python SDK, and Code Interpreter SDK in CI
resolve the latest TypeScript SDK at test time instead of using a pinned dependency and lockfile
use e2b_000000 as the local placeholder API key across E2E suites and documentation

Motivation

The compatibility suites previously tested fixed E2B client versions, which meant upstream compatibility regressions were only detected after manually updating those pins.

This change intentionally makes the suites follow the latest stable client releases. The TypeScript SDK is installed with e2b@latest while ignoring lockfiles, and the Python packages are upgraded on each CI run.

The placeholder API key now also follows the E2B key format expected by current clients while remaining a non-secret value for local AgentENV deployments.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/AgentENV/pull/4 **Author:** [@LSX-s-Software](https://github.com/LSX-s-Software) **Created:** 7/26/2026 **Status:** ✅ Merged **Merged:** 7/27/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `test/e2b` --- ### 📝 Commits (1) - [`cd32e5a`](https://github.com/kvcache-ai/AgentENV/commit/cd32e5a60fc14dba9f2c198f551d95557d57b23a) test: track latest E2B clients in compatibility tests ### 📊 Changes **8 files changed** (+13 additions, -951 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/integration-tests.yml` (+6 -4) 📝 `docs/src/configuration/env-vars.md` (+2 -2) 📝 `docs/src/integration/e2b-cli.md` (+1 -1) 📝 `docs/src/integration/e2b-sdk.md` (+1 -1) ➖ `scripts/tests/e2e/package-lock.json` (+0 -937) 📝 `scripts/tests/e2e/package.json` (+0 -3) 📝 `scripts/tests/e2e/suites/09_e2b_compat.sh` (+2 -2) 📝 `scripts/tests/e2e/suites/14_code_interpreter.sh` (+1 -1) </details> ### 📄 Description ## Summary - install the latest stable E2B CLI, Python SDK, and Code Interpreter SDK in CI - resolve the latest TypeScript SDK at test time instead of using a pinned dependency and lockfile - use `e2b_000000` as the local placeholder API key across E2E suites and documentation ## Motivation The compatibility suites previously tested fixed E2B client versions, which meant upstream compatibility regressions were only detected after manually updating those pins. This change intentionally makes the suites follow the latest stable client releases. The TypeScript SDK is installed with `e2b@latest` while ignoring lockfiles, and the Python packages are upgraded on each CI run. The placeholder API key now also follows the E2B key format expected by current clients while remaining a non-secret value for local AgentENV deployments. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-29 14:19:52 +00:00