## upgrade.UpgradeReport


What `Repo.apply_upgrade` did.


Usage

``` python
upgrade.UpgradeReport(
    from_version=0,
    to_version=0,
    renamed_pins=dict(),
    renamed_branches=dict(),
    rewritten_commits=dict(),
    refingerprinted=list(),
    rewritten_manifests=list(),
    rewritten_indexes=dict(),
    copied_listings=list(),
    failed=dict(),
    vcs_commit=None,
    plan=None
)
```


## Attributes


`from_version: int`  
`[tether] version` before.

`to_version: int`  
`[tether] version` after.

`renamed_pins: dict[str, str]`  
Old native ref -\> new native ref, per store.

`renamed_branches: dict[str, str]`  
Old working branch -\> new working branch.

`rewritten_commits: dict[str, str]`  
Old commit id -\> new commit id (history rewrite).

`refingerprinted: list[str]`  
Objects whose manifest state was recomputed (v3).

`rewritten_manifests: list[str]`  
Objects whose manifest lost its write policy (v3), moved or got an absolute path (v4), or had its state carried into the current form (v5).

`rewritten_indexes: dict[str, int]`  
Index file beside the repository lock -\> records given the identity their store has now (v5).

`copied_listings: list[str]`  
Listings stored again under the name their object's identity gives them now (v5).

`failed: dict[str, str]`  
Target -\> why a step did not happen.

`vcs_commit: str | None`  
The commit that records the upgraded working tree.

`plan: Plan | None`  
The plan that was applied.