chore: release packages

[btravers]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@unthrown/drizzle@0.1.0

Minor Changes

• 5c1b926: Add @unthrown/drizzle, a Drizzle ORM Postgres integration that replaces the
  stock drizzle-orm/node-postgres database rather than wrapping one: every method
  already speaks AsyncResult, so there is no try* prefix to learn and migrating
  a call site is an import change. Writes (insert, update, delete, raw
  db.execute, transaction) carry the five integrity-constraint
  SQLSTATEs as tagged errors — UniqueConstraintViolation (23505),
  ForeignKeyViolation (23503), NotNullViolation (23502, carrying column),
  CheckViolation (23514), ExclusionViolation (23P01) — while every
  infrastructure failure (deadlock, serialization failure, statement timeout,
  connection loss, a syntax error) is a Defect, so a retry lives in one
  recoverDefect wrapper instead of an arm at every call site. Reads (select,
  $count, db.query.*, refreshMaterializedView, and their prepared forms)
  infer E = never, enforced at runtime through fromSafePromise so the type
  cannot drift from what the runtime produces. Transactions follow the variants
  directly: Ok commits, Err and Defect both roll back, an Err re-surfaces
  typed, and there is deliberately no tx.rollback() — nesting is a savepoint.
  Also exports qualifyPgError for boundaries of your own, and keeps db.$client
  as the escape hatch to a stock drizzle database over the same pool.

  Every driver rejection is wrapped in drizzle's own DrizzleQueryError before
  triage, exactly as stock drizzle does, so a defect names the failing statement
  and its params — node-postgres' DatabaseError carries code/constraint/
  table/column/detail but not the SQL. The driver error stays one cause
  level down, which is where qualifyPgError already reads the SQLSTATE from.

  The exported pg-core classes are spelled uniformly PgUnthrown*
  (PgUnthrownSelectBase, PgUnthrownInsertBase, …, plus PgUnthrownDatabase,
  PgUnthrownSession, PgUnthrownPreparedQuery and
  PgUnthrownSafePreparedQuery), mirroring drizzle's own uniform PgAsync*
  tree; the node-postgres ones keep drizzle's NodePg… shape as
  NodePgUnthrown*. One concept, one name — settled before the first publish,
  since it is public API.

  drizzle-orm and pg are peer dependencies (^1.0.0-rc and ^8.16.0); the
  internals — which subclass drizzle's pg-core builder tree — were verified
  against drizzle-orm@1.0.0-rc.4.

[Copilot]

Pull request overview

This is an automated Changesets release PR to publish the initial @unthrown/drizzle@0.1.0 release by applying the generated version bump, changelog entry, and consuming the corresponding changeset.

Changes:

• Bump @unthrown/drizzle package version to 0.1.0.
• Add packages/drizzle/CHANGELOG.md with the 0.1.0 release notes.
• Remove the consumed Changesets entry (.changeset/great-hoops-hammer.md).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
packages/drizzle/package.json	Updates the package version to 0.1.0 for the release.
packages/drizzle/CHANGELOG.md	Introduces the 0.1.0 changelog entry describing the new package release.
.changeset/great-hoops-hammer.md	Removes the changeset after it has been applied to the release outputs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.