# `PhoenixKit.Migrations.Postgres.V153`
[🔗](https://github.com/BeamLabEU/phoenix_kit/blob/v2.13.7/lib/phoenix_kit/migrations/postgres/v153.ex#L1)

V153: folder header size defaults to small.

New folders now open with a small hero header (see the schema default on
`PhoenixKit.Modules.Storage.Folder`). This migration brings existing rows
and the DB column default in line:

  * **Column default** `phoenix_kit_media_folders.header_size` flips from
    `'medium'` (set in V134) to `'small'`, so raw inserts match the
    changeset default.

  * **Backfill** every folder currently on `'medium'` → `'small'`.
    `'medium'` was the *old default*, so a stored `'medium'` is
    indistinguishable from "never touched" — those reset to small.
    `'large'` was never a default, so any `'large'` is a deliberate
    choice and is left alone; existing `'small'` rows are unaffected.

There is no stored "user customised this" signal, so a folder someone
deliberately set to `'medium'` also resets — an accepted trade-off, since
medium and default-medium can't be told apart. Users can re-pick medium
from the header-size control any time.

Idempotent: the backfill's `WHERE header_size = 'medium'` and the default
swap are safe to re-run.

# `down`

Rolls V153 back.

Restores the column default to `'medium'` (its V134 value). **Lossy:** the
`medium → small` backfill is not reversed — the folders that were reset
can't be told apart from folders genuinely on small, so their sizes stay
as they are.

# `up`

---

*Consult [api-reference.md](api-reference.md) for complete listing*