[skip ci] Release new versions (sync repo with published packages)

[mishushakov]

Why

The Release run 27844631141 published all packages successfully but then failed at the final "Commit new versions" step — the version-bump commit-back to `main` was rejected as non-fast-forward (another PR landed on `main` during the release window).

As a result the registries are ahead of the repo:

Package	Published	Repo (main) before this PR
`e2b` (JS)	2.30.4 (npm)	2.30.3
`@e2b/cli`	2.12.2 (npm)	2.12.1
`e2b` (Python)	2.29.4 (PyPI)	2.29.3

The changeset `fix-logo-pypi-npm.md` was also never consumed and is still on `main`.

What this PR does

Replays exactly what the failed "Commit new versions" step would have committed — i.e. `pnpm run version` (changeset version + `postVersion` poetry sync) + lockfile update:

• Bumps `e2b` → 2.30.4, `@e2b/cli` → 2.12.2, `@e2b/python-sdk` → 2.29.4 (matching what's already published)
• Deletes the consumed changeset `fix-logo-pypi-npm.md`
• Updates `pnpm-lock.yaml` (CLI's `e2b` dep → 2.30.4)

No new packages are published by merging this — it only syncs the repo to the registries. Do not re-run the Release workflow for this changeset; the versions already exist on npm/PyPI.

[cursor]

PR Summary

Low Risk
Only version strings, dependency ranges, lockfile entries, and changeset cleanup—no runtime or API code in the diff.

Overview
Repo version fields were behind what Release already published because the post-publish commit to main failed (non-fast-forward). This change bumps e2b to 2.30.4, @e2b/cli to 2.12.2, and the Python SDK to 2.29.4 in package.json / pyproject.toml, points @e2b/cli at e2b ^2.30.4, refreshes pnpm-lock.yaml, and removes the consumed changeset .changeset/fix-logo-pypi-npm.md. No application source is modified; merging does not publish again.

^{Reviewed by Cursor Bugbot for commit c769422. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: c769422

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Package Artifacts

Built from 0246314. Download artifacts from this workflow run.

JS SDK (e2b@2.30.5-release-sync-2-30-4.0):

npm install ./e2b-2.30.5-release-sync-2-30-4.0.tgz

CLI (@e2b/cli@2.12.3-release-sync-2-30-4.0):

npm install ./e2b-cli-2.12.3-release-sync-2-30-4.0.tgz

Python SDK (e2b==2.29.4+release-sync-2-30-4):

pip install ./e2b-2.29.4+release.sync.2.30.4-py3-none-any.whl