fix(release): bump Code Interpreter Python past PyPI collision

[devin-ai-integration]

Summary

Add a patch changeset for @e2b/code-interpreter-python, advancing the next release from 2.9.2 to the available 2.9.3 version. Version 2.9.2 was already published by the pre-migration Code Interpreter repository, so the monorepo's differently built artifact cannot be uploaded under that immutable PyPI version.

Root-cause excerpt from Publish / Build and test SDK:

packages/code-interpreter-python postPublish: error: Local file and index file do not match for e2b_code_interpreter-2.9.2-py3-none-any.whl.
Local: sha256=2647134ef53a8bd718cf9f4ca216730521774fdc0685fb79ab4b031ec40b9554
Remote: sha256=1acf7be290050939ead3c1bae7f55c73433c2ee8e55c5e0e75d6d8e168b6bca0

Local verification: pnpm changeset status resolves only @e2b/code-interpreter-python as a patch release; repository format, lint, and typecheck pass.

Link to Devin session: https://app.devin.ai/sessions/66b7520fe2d546f09c3575440583087f
Open in Devin Desktop: https://app.devin.ai/desktop/session/66b7520fe2d546f09c3575440583087f?variant=devin

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[changeset-bot]

🦋 Changeset detected

Latest commit: b1732ec

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@e2b/code-interpreter-python	Patch

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

[devin-ai-integration]

TASTE.md review: the diff is a single release changeset (.changeset/code-interpreter-python-pypi-clash.md) touching no public SDK surface — no API shape, naming, error, timeout, config, module-structure, or docstring rules (T-1 through T-74) are in scope. 0 violations.

[github-actions]

Package Artifacts

Built from 015459a. Download artifacts from this workflow run.

JS SDK (e2b@2.46.2-devin-1787865524-code-interpreter-pypi-clash.0):

npm install ./e2b-2.46.2-devin-1787865524-code-interpreter-pypi-clash.0.tgz

CLI (@e2b/cli@2.18.1-devin-1787865524-code-interpreter-pypi-clash.0):

npm install ./e2b-cli-2.18.1-devin-1787865524-code-interpreter-pypi-clash.0.tgz

Code Interpreter JS SDK (@e2b/code-interpreter@2.7.3-devin-1787865524-code-interpreter-pypi-clash.0):

npm install ./e2b-code-interpreter-2.7.3-devin-1787865524-code-interpreter-pypi-clash.0.tgz

Desktop JS SDK (@e2b/desktop@2.3.4-devin-1787865524-code-interpreter-pypi-clash.0):

npm install ./e2b-desktop-2.3.4-devin-1787865524-code-interpreter-pypi-clash.0.tgz

Python SDK (e2b==2.46.1+devin.1787865524.code.interpreter.pypi.clash):

pip install ./e2b-2.46.1+devin.1787865524.code.interpreter.pypi.clash-py3-none-any.whl

Code Interpreter Python SDK (e2b-code-interpreter==2.9.2+devin.1787865524.code.interpreter.pypi.clash):

pip install ./e2b_code_interpreter-2.9.2+devin.1787865524.code.interpreter.pypi.clash-py3-none-any.whl

Desktop Python SDK (e2b-desktop==2.4.5+devin.1787865524.code.interpreter.pypi.clash):

pip install ./e2b_desktop-2.4.5+devin.1787865524.code.interpreter.pypi.clash-py3-none-any.whl

[claude]

Looks good — a straightforward changeset addition with no code changes. Reviewed the single new file: it correctly targets @ e2b/code-interpreter-python with a patch bump and clearly explains the PyPI version-clash rationale, consistent with the repo's changeset convention.

Extended reasoning...

Overview

The diff adds a single new file, .changeset/code-interpreter-python-pypi-clash.md, containing standard changeset frontmatter ('@ e2b/code-interpreter-python': patch) and a short description explaining that version 2.9.2 was already published to PyPI with different file contents from the pre-migration repo, so a patch bump is needed to avoid a uv publish --check-url mismatch on release. No source code, SDK implementation, spec files, or tests are touched.

Security risks

None. This is a release-metadata file only; it has no runtime effect and does not touch any code path.

Level of scrutiny

Low. This is exactly the kind of mechanical, self-contained change (a changeset addition) that the repo's own tooling expects for a patch release, and it matches the CLAUDE.md convention of generating a changeset via pnpm changeset when the public surface of an SDK package changes (or, in this case, when a release-only version bump is needed). There is no ambiguity in intent or content.

Other factors

No tests are needed since no code changed; format/lint/typecheck are moot for a markdown changeset file. The PR description's stated verification (pnpm changeset status resolving correctly) is plausible given the file's correct frontmatter syntax. No CODEOWNERS concerns apply to .changeset/ files in a way that would block this. The bug hunt reported no findings, and my own review of the diff confirms the change is trivial and correct.