Fix Python package name in changesets#261
Merged
matthewlouisbrockman merged 1 commit intomainfrom Apr 28, 2026
Merged
Conversation
PR SummaryLow Risk Overview No product/runtime behavior changes; this only affects which packages get patch bumps for the existing features described in the changesets. Reviewed by Cursor Bugbot for commit 79aa672. Bugbot is set up for automated code reviews on this repo. Configure here. |
Contributor
Author
|
i have no idea what claude code is doing |
djeebus
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix pending changesets to reference
@e2b/code-interpreter-pythoninstead of the PyPI package namee2b-code-interpreter.Changesets resolves package names from pnpm workspace
package.jsonfiles, notpyproject.toml, so the old name caused release planning to fail with “package e2b-code-interpreter is not in the workspace.”it'll just combine the changesets, leaving the old one in should be fine. i think it autodeletes so there's possibly some missing changesets that never deployed we might lose in the change logs.