v0.1.16

Keep the atlas range at ^0.3.x

atlas 0.4.0 was reconsidered as the patch it is: nothing in it breaks a
caller, and select(db.raw(...)) — the one behaviour that changed shape —
was a syntax error on Postgres, so nobody could depend on it.

Release 0.1.16

Accept atlas 0.4.0 alongside 0.3.x

A caret on a 0.x version is a ceiling, not a floor: ^0.3.0 excludes the
0.4.0 atlas is about to publish. Widened rather than moved, so this
resolves against the 0.3.12 on the registry today AND against 0.4.0 once
it lands — there is no window where CI, which installs from the registry,
resolves nothing.

Lint this package the way its own repository will

biome's configuration lived only at the workspace root. This package is
built from its own repository, where that file does not exist and biome
falls back to its defaults — so lint in CI has been checking a different
set of rules from lint here, and the bans this project actually cares
about were never enforced where it counts.

The config is now the package's own, and says the same thing the root one
did.

Declare what CI has to install

Each package is its own repository: pnpm install there sees only this
file, so a dependency the workspace happened to hoist locally is simply
absent in CI. --coverage needs @vitest/coverage-v8 named here, and an
optional peer a test imports has to be a devDependency as well — optional
is exactly what keeps it from being installed.

---

Changes since v0.1.15.