Mish Ushakov
3cb6ca5f92
## Why The Release run [27844631141](https://github.com/e2b-dev/E2B/actions/runs/27844631141/job/82412481993) **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.
16 lines
555 B
JSON
16 lines
555 B
JSON
{
|
|
"name": "@e2b/python-sdk",
|
|
"private": true,
|
|
"version": "2.29.4",
|
|
"scripts": {
|
|
"example": "poetry run python example.py",
|
|
"test": "poetry run pytest -n 4 --verbose -x",
|
|
"postVersion": "poetry version $(pnpm pkg get version --workspaces=false | tr -d \\\")",
|
|
"postPublish": "poetry build && poetry config pypi-token.pypi ${PYPI_TOKEN} && poetry publish --skip-existing",
|
|
"pretest": "poetry install",
|
|
"typecheck": "poetry run make typecheck",
|
|
"lint": "poetry run make lint",
|
|
"format": "poetry run make format"
|
|
}
|
|
}
|