Repository navigation
Releases
BranchRift v0.4.2
BranchRift v0.4.2 - maintenance release
Fixed:
- Dirty/unmerged LFS files no longer falsely report ready (#21).
- Mixed Unicode and escaped Git paths decode correctly (#23).
- Common dependency/build manifests are classified correctly (#24).
Documentation:
- Clarified configured Git clean-filter execution risks.
- Clarified pipx and pytest environment requirements.
No new features or intentional JSON schema changes.
BranchRift v0.4.1
Maintenance release: reliability and evidence correctness.
- Fix unified-diff hunk content being mistaken for file headers (#17).
- Stabilize change-fact paths under user Git prefix settings (#18).
- Display unknown readiness and prioritize binary-sensitive overlaps (#19).
No new features or intentional CLI/JSON schema changes.
BranchRift v0.4.0
What's new
- Opt-in Git merge simulation with CLEAN / CONFLICTS / UNKNOWN / ERROR results.
- Experimental merged-tree pytest verification for trusted Python repositories.
- Separate Git merge and pytest outcomes, including CLEAN + FAIL.
- Evidence metadata, bounded test output, and merged-source import precedence.
- Improved README onboarding and explicit safety limitations.
Verification
- 241 local tests passed.
- 14/14 PR checks passed.
- Independent Git merge-tree verification on a real public PR.
- Controlled CLEAN + FAIL regression scenario reproduced.
Limitations
- No security sandbox or automatic CI gate.
- No external user adoption or measured time savings claimed.
- Experimental pytest verification only for trusted repositories.
BranchRift v0.3.0
BranchRift v0.3.0
BranchRift is a read-only Git pre-integration risk CLI. This release focuses on real-repository correctness and easier first-run behavior, not new risk-prediction claims.
Notable improvements
- Default base behavior has changed. Running
branchriftwithout--basenow uses the locally recordedorigin/HEAD(or the only remote's HEAD). BranchRift never guessesmainordevwhen local metadata is missing or ambiguous. Usebranchrift --base devto retain the former implicitdevbehavior. - Repository-root path handling is correct when launched from nested directories.
- Binary inspection reads only the small prefix needed for LFS pointer detection, not an entire asset.
- Unicode and renamed Git paths are handled using NUL-delimited status and attribute records.
- Unreadable binaries stay unknown / require attention instead of being reported ready.
- Invalid ownership match types produce controlled configuration errors.
Verification
- 195/195 local pytest tests passed on Windows.
- PR #6 and #7 each passed 14/14 GitHub CI checks across Linux, Windows, and installed-wheel smoke.
- Four distinct real repositories passed read-only smoke checks, including Unreal project assets.
- A disposable, diverged Unreal repository test independently confirmed one
.umapsame-path, binary-sensitive collision and no false collision on a base-only.uasset.
Limitations
BranchRift does not guarantee a merge conflict, resolve Unreal binary assets, inspect their semantics, verify Unreal asset loadability, or prove full Git LFS hydration. Real-world team adoption remains unverified.
See CHANGELOG.md for details.
BranchRift v0.2.1
BranchRift v0.2.1
Added
- Zero-config analysis when
.preflight.jsonis absent. - Repository-root discovery for the default
.preflight.json, including runs from nested directories. - Structured ownership policy states:
not_configured,configured_empty, andconfigured. - Structured per-path ownership results:
known,not_configured, andno_match. - Structured governance output with explicit evaluation status and ownership policy status.
- Public report
schema_versionset to1.0. - Ownership status counts in report summaries.
Changed
- Ownership configuration is now optional.
- Missing ownership configuration no longer creates false ownership gaps, governance escalation, or manual-review noise.
- Governance decisions now use structured ownership state instead of the legacy
Unknownsentinel. - Explicit
--configpaths remain strict.
Compatibility
- Legacy
ownerandgovernance_statusfields remain available. - The legacy
preflightCLI command remains available.
Validation
- 182 tests passed locally.
- Linux CI passed on Python 3.10, 3.11, 3.12, and 3.13.
- Windows CI passed on Python 3.10 and 3.13.
- Clean built-wheel installation and CLI smoke tests passed.
- BranchRift successfully dogfooded the release against its own repository.
BranchRift v0.2.0
BranchRift v0.2.0
Repo Preflight is now BranchRift.
Changed
- Renamed the public product from Repo Preflight to BranchRift.
- The PyPI distribution is now
branchrift. - Added
branchriftas the primary CLI command. - Retained
preflightas a compatibility CLI alias. - The internal Python package remains
preflight. - The configuration filename remains
.preflight.json.
Compatibility
Existing analysis behavior is intentionally unchanged.
This release does not intentionally change:
- Git topology analysis
- same-path collision semantics
- ownership or governance behavior
- Git LFS readiness
- JSON output semantics
- exit-code behavior
Install
pipx install branchriftRepo Preflight v0.1.9
Highlights
Repo Preflight v0.1.9 is a focused correctness, compatibility, and output-resilience release based on real-repository dogfooding and targeted regression testing.
File-type prefix correctness
- Canonicalizes file-type path prefixes consistently.
- Equivalent spellings such as
src,src/, andsrc\can no longer change classification or specificity. - Rejects prefixes that canonicalize to an empty path.
- Existing canonical configurations keep their existing behavior.
Detached HEAD support
- SHA-based analysis now works from detached HEAD checkouts.
- Detached checkouts are reported as
DETACHEDinstead of failing before analysis. - Topology, collisions, change facts, provenance, and readiness remain revision/SHA based.
Generic Git LFS readiness
- LFS transport state is now independent from semantic file type.
- LFS-managed files such as
.wavcan receive readiness information while remainingfile_type: other. - Technical-risk semantics are unchanged.
- Historical revisions continue to avoid inheriting hydration state from the current checkout.
Cleaner exact change facts
- Valid Git LFS pointer transport metadata is no longer emitted as meaningful exact change facts.
- Pointer recognition remains conservative and requires a valid pointer structure.
- Ordinary text containing words such as
sizeoroidis not suppressed.
Bounded terminal output
- Manual-review output is capped at 20 paths in the terminal.
- The total count and omitted count are shown when the list is larger.
- JSON continues to contain the complete manual-review list.
Windows terminal resilience
- Terminal reports no longer crash when the active Windows code page cannot encode a valid Unicode character.
- Supported characters remain unchanged.
- Unsupported characters are escaped deterministically at the output boundary.
- UTF-8 terminals continue to preserve Unicode normally.
Validation
- 167 tests passing locally.
- Ubuntu CI: Python 3.10, 3.11, 3.12, and 3.13.
- Windows CI: Python 3.10 and 3.13.
- Clean built-wheel smoke test passed.
- Clean wheel installation verified outside the source tree.
- Dogfooded against Repo Preflight itself.
- Dogfooded against Breaking Line current and historical revisions.
- Tested with 10,000 changed files without identifying a scaling defect.
- Tested LFS attribute handling with up to 1,000 paths.
Repo Preflight remains read-only and advisory.
Repo Preflight v0.1.8
Highlights
Repo Preflight v0.1.8 strengthens revision-aware repository analysis and real-world portability.
Exact change facts
- Reports conservative exact change facts from the merge-base diff.
- Pairs obvious scalar value changes such as
count: 1 -> 2. - Falls back to added/removed lines when a safe semantic pairing cannot be made.
- Does not invent internal semantics for binary assets, maps, or other binary files.
Binary and LFS readiness
- Reports binary/LFS readiness for asset and map changes.
- LFS attributes are resolved from the analyzed head revision.
- Historical revisions do not inherit hydration state from the current checkout.
- Historical working-tree-dependent readiness remains
unknownwithanalyzed_head_not_current_checkout.
Revision provenance
- Reports requested base/head refs and resolved commit SHAs.
- Reports merge-base comparison provenance.
- Explicitly states whether the analyzed head is the current checkout.
Git execution resilience
- Adds operation-aware Git timeout budgets:
- 15s fast operations
- 30s normal analysis
- 90s expensive diff/collision/LFS inspection
- Required analysis failures remain fatal.
- Optional LFS inspection failures degrade conservatively instead of failing unrelated source analysis.
Windows and Unicode portability
- Git output is decoded as UTF-8 across platforms.
- Valid Unicode content and Git-quoted Unicode paths survive correctly on Windows.
- Missing stdout becomes a controlled
GitError. - Invalid UTF-8 bytes are replaced rather than crashing the CLI.
Validation
- 139 tests passing locally.
- Ubuntu CI: Python 3.10, 3.11, 3.12, 3.13.
- Windows CI: Python 3.10 and 3.13.
- Clean built-wheel smoke test on Windows.
- Dogfooded against Project2.
- Dogfooded against Breaking Line, including a 657-file historical range.
- Historical LFS provenance and cross-checkout isolation verified.
Known limitations
- Historical working-tree-dependent binary readiness remains intentionally unknown.
- Non-UTF-8 POSIX filename bytes are not preserved losslessly.
.wavLFS-pointer fact polish and long manual-review list compression are deferred.
Repo Preflight remains read-only and advisory.
Repo Preflight v0.1.7
Repo Preflight v0.1.7 adds same-path branch collision detection.
Added
- Detect repository paths changed on both sides since the merge-base.
- Report collisions as a separate advisory integration signal.
- Mark
assetandmapcollisions asBINARY-SENSITIVE. - Include deterministic collision data in terminal and JSON output.
- Support collision analysis with explicit
--headwithout checkout.
Semantics
A collision means the same repository path changed on both sides since the merge-base.
It does not mean a guaranteed Git textual merge conflict.
Rename handling in v0.1.7 is intentionally conservative and path-string based (--no-renames), not rename-identity aware.
Validation
- 75 tests passing.
- ADD/ADD collision coverage.
- DELETE/MODIFY collision coverage.
- Rename path-contract coverage.
- GitHub Actions passing on Python 3.10–3.13.
- Technical risk and governance behavior unchanged.
Repo Preflight remains read-only and advisory.
Repo Preflight v0.1.6
Repo Preflight v0.1.6 adds Git topology awareness to integration preflight analysis.
Added
- Resolved base and head commit SHAs.
- Merge-base reporting.
- Ahead/behind commit counts.
- Explicit topology relationships:
SAMELINEARHEAD_BEHINDDIVERGED
- Fast-forward eligibility reporting in terminal and JSON output.
Improved
- Ownership prefix rules now use canonical path-prefix semantics.
- Equivalent prefixes such as
src,src/, andsrc\are treated consistently. - Prefixes that canonicalize to an empty path are rejected.
- Ownership specificity is no longer affected by trailing separators.
Dogfooding
v0.1.6 was used to inspect its own feature branch before integration.
Observed topology:
- Behind: 0
- Ahead: 1
- Relationship:
LINEAR - FF eligible:
YES
The branch was then integrated using a fast-forward-only merge.
Validation
- 60 tests passing locally.
- GitHub Actions passing on Python 3.10, 3.11, 3.12, and 3.13.
- Real repository topology output matched the Git commit graph.
Repo Preflight remains read-only and advisory. It does not merge, checkout, pull, fetch, push, or mutate the inspected repository.