localize_units_sql

# Changelog

**Note** that `localize_units_sql` is supported on Elixir 1.17 and later only.

## Localize Units SQL v2.0.0

This is the changelog for Localize Units SQL v2.0.0 released on April 24th, 2026.

### Breaking changes

* The package has been renamed from `ex_cldr_units_sql` to `localize_units_sql`. The `Cldr.Unit.*` modules are now `Localize.Unit.*` (for example `Cldr.Unit.Ecto.Composite.Type` becomes `Localize.Unit.Ecto.Composite.Type`). Existing schema and migration references must be updated.

* Supported on Elixir 1.17 or later only.

* Requires the unified [localize](https://hex.pm/packages/localize) package in place of the `ex_cldr` family of dependencies. The CLDR backend module (e.g. `MyApp.Cldr`) and its configuration are no longer used. Configure locales through `config :localize` instead.

* `Localize.Unit` uses string unit identifiers (for example `"meter"`) and string usage values (for example `"person"`), rather than atoms. Code that previously passed `:meter` or `usage: :person` should pass `"meter"` / `usage: "person"`.

* `Localize.Unit.new/2,3` takes the value as the first argument and the unit identifier as the second. The `Cldr.Unit.new(:meter, 100)` form is no longer valid — use `Localize.Unit.new(100, "meter")`.

* The `:unit` field on the struct has been renamed to `:name`.

* `jason` is no longer a declared dependency. Postgrex defaults to `Jason` for `json`/`jsonb` columns; configure `config :postgrex, :json_library, JSON` (Elixir 1.18+) and run `mix deps.compile postgrex --force` once since Postgrex captures this setting at compile time.

### Enhancements

* The Postgres composite type names (`cldr_unit`, `cldr_unit_with_usage`) and aggregate function names are unchanged, so existing databases do not require a schema migration.