chore: bump @e2b/code-interpreter past npm-published 2.7.2 - #1781
chore: bump @e2b/code-interpreter past npm-published 2.7.2#1781devin-ai-integration[bot] wants to merge 2 commits into
Conversation
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
🦋 Changeset detectedLatest commit: 26a2bef The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
TASTE.md review: this PR only bumps package versions and changelog headings for the migrated Code Interpreter and Desktop packages (package.json, pyproject.toml, uv.lock, CHANGELOG.md). It touches no public SDK API surface, so none of the TASTE.md design principles (T-1 through T-60) are implicated. No violations found.
Package ArtifactsBuilt from bcd4b83. Download artifacts from this workflow run. JS SDK ( npm install ./e2b-2.46.2-devin-1787862408-fix-migrated-sdk-versions.0.tgzCLI ( npm install ./e2b-cli-2.18.1-devin-1787862408-fix-migrated-sdk-versions.0.tgzCode Interpreter JS SDK ( npm install ./e2b-code-interpreter-2.7.3-devin-1787862408-fix-migrated-sdk-versions.0.tgzDesktop JS SDK ( npm install ./e2b-desktop-2.3.5-devin-1787862408-fix-migrated-sdk-versions.0.tgzPython SDK ( pip install ./e2b-2.46.4+devin.1787862408.fix.migrated.sdk.versions-py3-none-any.whlCode Interpreter Python SDK ( pip install ./e2b_code_interpreter-2.9.3+devin.1787862408.fix.migrated.sdk.versions-py3-none-any.whlDesktop Python SDK ( pip install ./e2b_desktop-2.4.6+devin.1787862408.fix.migrated.sdk.versions-py3-none-any.whl |
There was a problem hiding this comment.
Looks good, straightforward version-bump/changelog release commit. Reviewed the package.json/pyproject.toml version bumps, CHANGELOG.md heading updates, and the uv.lock diffs (regenerated resolver metadata plus the e2b/e2b-code-interpreter/e2b-desktop version bumps) — no source code, tests, or specs were touched, consistent with the stated goal of moving the migrated packages onto unpublished version numbers.
Extended reasoning...
Overview
The diff touches only package.json, pyproject.toml, CHANGELOG.md, and uv.lock files across four packages (code-interpreter-js, code-interpreter-python, desktop-js, desktop-python). Each package's version was bumped by one more patch level (e.g. 2.7.2→2.7.3), and the CHANGELOG.md heading for the most recent entry was relabeled to match. No .ts/.js/.py source files were modified.
Security risks
None. There is no code path change, no new dependency added, no auth/crypto/permissions logic touched. The uv.lock changes are resolver-generated marker/version metadata for existing dependencies (numpy/contourpy/matplotlib markers, and the editable e2b/e2b-code-interpreter/e2b-desktop self-version bumps), not new package additions.
Level of scrutiny
Low. This is a mechanical release/version-bump commit consistent with the PR's stated purpose (moving versions past ones already published from the pre-migration standalone repos, to unblock the next release). I verified the actual diffs for all package.json/pyproject.toml/CHANGELOG.md files and the two uv.lock files match this description exactly — simple version string bumps and lockfile metadata refresh, no functional edits.
Other factors
No spec/ files, no CLAUDE.md, and no CODEOWNERS-sensitive paths (auth, SDK core logic) were touched. No changeset is needed for this diff since it's not a public-surface change to cli/js-sdk/python-sdk, and it appears to be the release-bump artifact itself. No prior review comments exist to reconcile (this is the first pass), and the PR is bot-authored release automation, which is a common, low-risk pattern in this repo.
19ece73 to
4671f1e
Compare
|
can you check if this is still relevant? |
…egistry-published versions Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
4671f1e to
26a2bef
Compare
|
Partly — I rebased and narrowed it to
Separately, the tag |
Summary
Still relevant, but only for
@e2b/code-interpreter— rebased and narrowed to that one package.Three of the four packages migrated in #1768 have since been moved off the version numbers the pre-migration repos had already published (#1782, #1785, and subsequent releases):
@e2b/desktop-pythonis at 2.4.6,@e2b/code-interpreter-pythonat 2.9.3,@e2b/desktopat 2.3.4 — all unpublished numbers, so they will release normally.@e2b/code-interpreteris the leftover: repo says 2.7.2 and npm's 2.7.2 is the olde2b-dev/code-interpreterbuild from 2026-08-26T12:29:50Z, sochangeset publishkeeps skipping it —and its monorepo changelog entries (the migration itself, plus the Deno / workerd mid-request-kill
TimeoutErrordetection from #1771) are on no registry. The JS packages have not been throughchangeset publishsince that failed run — the last green Release (run 33680862316) was the python-sdk-only isolated publish from #1799 — so nothing has cleared this in the meantime.One patch changeset, verified with
pnpm changeset status --verbose:Still open for a human: the tag
@e2b/desktop-python@2.4.4onmainpoints at content that was never published anywhere.Link to Devin session: https://app.devin.ai/sessions/c79435a20a9b4389a0d18712c9c8844d
Open in Devin Desktop: https://app.devin.ai/desktop/session/c79435a20a9b4389a0d18712c9c8844d?variant=devin