# Shared dependency change: [PACKAGE ID FROM VERSION TO VERSION]

> Team document template. Copy this file per dependency move, fill every
> bracketed field, and store the result beside the consuming package. The
> engine never reads this file: it records why a shared dependency moved
> and what proved the move safe, not a package format.

How to use: open this record before changing the pin, close it after the
verification runs pass. One record per dependency per move; never bundle
two shared moves into one record.

- Dependency: [package id, e.g. labparcels.registry]
- Move: [e.g. 0.1.0 -> 0.2.0]
- Consumer: [package id of the package moving]
- Author: [who performs the move]
- Date opened: [YYYY-MM-DD]
- Status: [open | verified | rolled back]

## 1. Reason

[Why move? One paragraph: the fix, the new words, or the withdrawal that
forces this consumer off the old version. Link the upstream release note
by name.]

## 2. Blast radius

| Consumer or case | Pinned version after this move | Needs its own record? |
|---|---|---|
| [this package] | [new version] | [no: this record covers it] |
| [affected case package] | [new version] | [yes: named below] |

[If the shared package has other consumers, list them and say whether
they move now or stay pinned; staying pinned is allowed and needs no
record here.]

## 3. Pre-move readings

Take these before editing the pin (paste exact outputs in fences):

```text
[paste: outdated report showing the old pin and the newer version]
```

```text
[paste: current test output on the old pin, for comparison]
```

## 4. The move

Steps (edit, refresh the lock, rerun):

```text
[paste: the commands run and their exact outputs]
```

Post-move readings (same commands as section 3, on the new pin):

```text
[paste: test output on the new pin]
```

```text
[paste: lock check output on the new pin]
```

## 5. Rollback

[How to return to the old pin: the exact version to restore and the
command that refreshes the lock back. One paragraph; write it before you
need it.]

## 6. Sign-off

- Reviewer: [name]
- Date closed: [YYYY-MM-DD]
- Outcome: [verified: the readings above pass on the new pin | rolled back]
- Notes: [one line, or "none"]