Repository navigation
chore(code-interpreter-python): add @e2b/python-sdk workspace dependency #1968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,6 +2,9 @@ | |
| "name": "@e2b/code-interpreter-python", | ||
| "private": true, | ||
| "version": "2.10.4", | ||
| "dependencies": { | ||
| "@e2b/python-sdk": "workspace:*" | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🔴 After merging, a release with only a python-sdk changeset also publishes a new e2b-code-interpreter to PyPI, and its test suite is skipped. Changesets reads Why this was flaggedTrigger: a changeset that bumps only Verification: The diff adds "@ e2b/python-sdk": "workspace:*" in packages/code-interpreter-python/package.json:5-7, so any python-sdk bump gives the dependent a patch release. release.yml:110 runs is_release_for_package.sh, which reads only the raw changeset files, so it outputs false. The code-interpreter-python-tests job (release.yml:185-190) is skipped, and publish (release.yml:231) still runs. |
||
| }, | ||
| "scripts": { | ||
| "test": "uv run pytest -n 4 --verbose -x", | ||
| "postVersion": "uv version --frozen $(pnpm pkg get version --workspaces=false | tr -d \\\")", | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the version actually needed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
versionfield was already there (not added by this PR). It's used by thepostVersionscript below, which syncs it intopyproject.tomlviauv versionon release — same pattern aspackages/python-sdk. Only thedependenciesblock is new.