auto-rebase-ai
auto-rebase-ai is a local PyPI package for maintaining long-lived forks with
the same four-part architecture described in goal.md, reference.md, and the
diagram in image.png.
auto-rebase = orchestrator
detect-upstream-base = disturbance detection
rebase-assistant = controller
local-test-runner = measurement
The orchestrator finds the fork's current upstream base, resolves a newer target ref, delegates the rebase to the controller, and writes a final report. The controller owns the baseline gate, rebase, conflict handling, Codex repair loop, and summary. The local test runner only measures configured checks.
Install
pipx install auto-rebase-ai
or:
uv tool install auto-rebase-ai
Usage
Inside a forked repository:
auto-rebase init
auto-rebase doctor
auto-rebase run
The default command launches the simple TUI:
auto-rebase
Safety
Version 0.1 never pushes automatically, refuses a dirty working tree except
for generated .auto-rebase/ artifacts, creates a backup branch before rebasing,
and writes repair packets with configured secret redaction.
Release
Before publishing:
uv run --extra dev pytest
uv run --extra dev ruff check .
uv build
Verify the built wheel through the tool-install path:
UV_TOOL_DIR=/tmp/auto-rebase-tool \
UV_TOOL_BIN_DIR=/tmp/auto-rebase-tool-bin \
uv tool install dist/auto_rebase_ai-0.1.1-py3-none-any.whl
/tmp/auto-rebase-tool-bin/auto-rebase init
Publish to PyPI after the package owner has configured credentials:
uv publish
1 maintainer
Metadata
1 maintainer
Release files for auto-rebase-ai 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| auto_rebase_ai-0.1.1.tar.gz | 620.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auto_rebase_ai-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 650.6 kB
Release files / auto_rebase_ai-0.1.1.tar.gz
| Download URL | auto_rebase_ai-0.1.1.tar.gz |
|---|---|
| Size | 620.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a31a7b446870ae01b55bc029b8b3955c1284897c0d08931c0b5f7742b0c8f05d
|
|
BLAKE2b-256 checksum How to use checksums |
ca67da783eacd141b6f03b7d66046fcaa3ef2d4478df167fb1b1cd5b3f9e1657
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.22 {"installer":{"name":"uv","version":"0.9.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / auto_rebase_ai-0.1.1-py3-none-any.whl
| Download URL | auto_rebase_ai-0.1.1-py3-none-any.whl |
|---|---|
| Size | 29.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b38369b65f1e6571bf62e9c257ff14a627fb2b6e42d31d850b370e338e32558c
|
|
BLAKE2b-256 checksum How to use checksums |
9a0dddd6bfa8d4498e5d36f56f5ea7a30c52f4abfd4bfadfb5a65a0be43629ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.22 {"installer":{"name":"uv","version":"0.9.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for auto-rebase-ai 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
