Fix npm version import and bump to v0.1.4 - #10
Merged
Conversation
Adds a self-update command that checks PyPI for the latest version and runs the appropriate package manager to update. Auto-detects the install method (pipx, brew, npm, or pip) and runs the matching upgrade command. Also clears the update cache after a successful update so the notification banner doesn't linger. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add _get_version() fallback that reads __init__.py when the rpr package isn't on the Python path (npm shim runs cli.py directly). Bump version to 0.1.4 across all manifests to sync with npm registry. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
ModuleNotFoundError: No module named 'rpr'when running via npm — adds_get_version()fallback that parses the sibling__init__.pyinstead of requiring therprpackage on the Python path0.1.4across__init__.py,pyproject.toml, andpackage.jsonto sync with npm registry (0.1.3 already published)rpr updateself-update command, background update notifications, review depth modesTest plan
rpr <PR>no longer throwsModuleNotFoundErroron the background update checkrpr updateworks when installed via npmrpr <PR> --depth quickworks in the npm-installed version🤖 Generated with Claude Code