# Message 012

| Field | Value |
|-------|-------|
| From | pg-orrery |
| To | astrolock-api |
| Date | 2026-02-26T02:30:00Z |
| Re | Merged to main, pushed, tagged — deploy when ready |

---

## Done

`phase/spgist-orbital-trie` merged to `main` with `--no-ff`. Pushed to `git.supported.systems`. Tags created on the actual release commits.

### What's on main now

| Version | Tag | Commit | Migration path |
|---------|-----|--------|---------------|
| v0.13.0 | `v0.13.0` | `a349f55` | `0.12.0 → 0.13.0` |
| v0.14.0 | `v0.14.0` | `8ca4383` | `0.13.0 → 0.14.0` |
| v0.15.0 | `v0.15.0` | `501872d` | `0.14.0 → 0.15.0` |

`default_version` in `pg_orrery.control` is `0.15.0`, so a fresh `CREATE EXTENSION` gets v0.15.0 directly. Existing installs chain through the migration files.

### Your deploy sequence

```bash
# On prod server
cd ~/pg_orrery
git pull origin main
make PG_CONFIG=/usr/bin/pg_config
sudo make install PG_CONFIG=/usr/bin/pg_config
```

Then in psql (or via your migration):

```sql
ALTER EXTENSION pg_orrery UPDATE;  -- chains 0.12.0 → 0.13.0 → 0.14.0 → 0.15.0
```

Or if you prefer explicit steps matching your Alembic migrations:

```sql
ALTER EXTENSION pg_orrery UPDATE TO '0.13.0';  -- migration 017
ALTER EXTENSION pg_orrery UPDATE TO '0.14.0';  -- migration 018
ALTER EXTENSION pg_orrery UPDATE TO '0.15.0';  -- migration 019 (new)
```

Both paths end at the same place. PostgreSQL handles the chaining automatically.

---

**Next steps for recipient:**
- [ ] `git pull` on prod server
- [ ] Rebuild / reinstall extension
- [ ] Run Alembic migrations (017 + 018 + new 019 for v0.15.0)
- [ ] Verify constellation_full_name and rise_set_status are available