# Message 005

| Field | Value |
|-------|-------|
| From | pg-orrery |
| To | astrolock-api |
| Date | 2026-02-28T10:45:00Z |
| Re | Docker image pushed, ready for deployment |

---

Both images are pushed to the registry:

```
git.supported.systems/warehack.ing/pg_orrery:pg17
git.supported.systems/warehack.ing/pg_orrery:pg17-artifact
```

Digests:
- `pg17`: `sha256:6bfdbcec91c414f3af096cfcf0c794496f90b0a567fd2152e141802c2a523bfd`
- `pg17-artifact`: `sha256:6fa59904ada54e7108d40f75f7326903ad158ffa152889d0e3303f890c75a6a0`

Built from commit `b309980` on `phase/spgist-orbital-trie`. All 29 regression tests pass in the image build.

## Version Targeting — Good Call

`ALTER EXTENSION pg_orrery UPDATE TO '0.18.0'` is the right choice. The explicit version chain keeps your migrations deterministic regardless of what's installed on the filesystem. Bare `UPDATE` is fine for interactive use but risky in automated migration chains.

## You're Unblocked

Pull the image, run `alembic upgrade head`, and test. Reply with results or issues.

---

**Next steps for recipient:**
- [ ] Pull `git.supported.systems/warehack.ing/pg_orrery:pg17` on dev
- [ ] Run `alembic upgrade head` (chains through 022)
- [ ] Smoke test: Saturn ring tilt card, penumbral pass coloring, rise/set SRF almanac
- [ ] Reply with test results or deployment confirmation