Version Packages

[github-actions]

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

@ingram-tech/nk-db@1.0.0

Major Changes

• beb294e: Drop Supabase-era compatibility. Breaking:

  • Connection string is DATABASE_URL only. The POSTGRES_URL_NON_POOLING
    and POSTGRES_URL fallbacks (the Supabase integration's autopopulated vars)
    are no longer read by getDatabaseUrl / dbEnv. Set DATABASE_URL.
  • Removed configureTimestampsAsStrings() (and the ./types module). It was
    a shim for Supabase-generated row types that declared timestamps as string.
    On the golden path, express this per-column with Drizzle's
    timestamp(..., { mode: "string" }); the pgTimestampToIso /
    pgNumericToNumber response-boundary coercions remain for strict schemas.

  No behavioral change to the pool, RLS helpers, or queries — only doc comments
  were reworded to drop Supabase/PostgREST framing.

@ingram-tech/nk-auth@0.9.0

Minor Changes

• 89268a8: Add passkeyOptionsForBaseUrl(baseURL, rpName): derives the passkey plugin's
  rpID (the base URL's hostname — the WebAuthn effective domain, no scheme or
  port) and origin (the URL itself) from a single base URL, keeping them in
  lockstep. Covers the common single-origin site so consumers no longer hand-roll
  new URL(baseURL).hostname. Multi-origin / parent-registrable-domain sites
  still call makePasskeyOptions with explicit values.

Patch Changes

• beb294e: Mark bcryptPassword as legacy support only (@deprecated): it exists
  solely so sites with pre-existing bcrypt hashes keep verifying. New sites should
  omit it and use Better Auth's default scrypt. The README's canonical lib/auth.ts
  no longer wires it, and a new "Migrating bcrypt passwords to scrypt" section
  documents the path (a dual-format verifier + lazy rehash-on-login or a reset
  campaign; Better Auth has the reset flow natively but no rehash-on-login and no
  "must reset" gate). bcryptPassword still works — no API change.

  Also drops the optional @supabase/supabase-js peer dependency (and the
  "Supabase RLS bridge" mention in the package description); the fleet is fully off
  Supabase, and RLS now lives in @ingram-tech/nk-db (withRls /
  withRlsTransaction).

• Updated dependencies [beb294e]

  • @ingram-tech/nk-db@1.0.0

@ingram-tech/nk-api@0.2.2

Patch Changes

• beb294e: Docs/metadata only: reword the package description, README, and source comments
  to describe nk-api as the alternative to an auto-generated REST API rather than
  "a PostgREST-style auto API." No code change.

@ingram-tech/nk-dev@0.2.4

Patch Changes

• beb294e: Remove the @supabase/supabase-js no-restricted-imports rule from the tier-b
  oxlint config — the fleet no longer uses supabase-js, so the guardrail is moot.
  The pg Pool/Client restriction (use createPool from nk-db) is unchanged.

@ingram-tech/nk-marketing@0.2.2

Patch Changes

• beb294e: Docs/comments only: drop the "successor to @ingram-tech/newsletter (which was
  Supabase-bound)" framing from the README and migration header, and remove the
  stale reference to nk-db's removed configureTimestampsAsStrings helper. No code
  change.