Skip to content

Version Packages - #54

Merged
Jerome Leclanche (jleclanche) merged 1 commit into
mainfrom
changeset-release/main
Sep 13, 2026
Merged

Jerome Leclanche (jleclanche) merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

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-auth@0.17.0

Minor Changes

  • ceb2ac6: Better Auth 1.7.4, and the guards that keep package and schema together.

    • 0003_better_auth_1_7_3 relaxes the 1.7 account identity constraint 0002 set: the (issuer, accountId) unique index and the NOT NULL on account.issuer are dropped. Better Auth 1.7.3 reverted issuer-scoped identity (accounts are keyed on (providerId, accountId) again, as in 1.6) and never writes the column, so 0002's constraint rejects every sign-up on 1.7.3+. The delta is safe under 1.7.2 too, so the order is migrate, then deploy. The column stays, nullable and unread; dropping it is a later optional delta.
    • better-auth and @better-auth/passkey are pinned to exactly 1.7.4 in peerDependencies. A site pins the same exact version; nk doctor (nk-dev 0.17) fails on a differing pin or a range. Every Better Auth bump ships as an nk-auth release with its chain delta, never as a site-level change.
    • createAuthHelpers checks the chain once per process, on the first session read: when the instance's database is a pg Pool and the database records the nk-auth chain, a journal behind the installed package throws the new AuthChainNotAppliedError naming the missing files, so "deployed before migrating" fails loudly instead of at a customer's sign-in. A site that owns the auth tables in its own baseline (no nk-auth journal) is skipped. assertAuthChainApplied(pool) is exported for instrumentation.ts or a health check; chainCheck: false opts out.
    • The migration test now also lists every column the chain carries that the pinned Better Auth does not model, so a relic cannot accumulate unnoticed.

Patch Changes

  • fed2c3c: Raise dependency floors: zod ^4.6.4, jose ^6.2.12, stripe ^22.6.2,
    intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
    oxfmt ^0.67 and knip ^6.35. No API change.
  • a288841: createAuthMiddleware detects the session cookie under sessionCookiePrefix, not only the default better-auth name. An app with its own advanced.cookiePrefix previously looped between the gate (no cookie seen) and the server guard (valid session).
  • c3554e1: Raise the react / react-dom peer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.
  • Updated dependencies [fed2c3c]
    • @ingram-tech/nk-db@2.1.3

@ingram-tech/nk-dev@0.17.0

Minor Changes

  • 52354ea: nk doctor fails a site whose better-auth / @better-auth/passkey is declared at any version or range other than the exact one the installed nk-auth pins in its peerDependencies (--fix pins it). Better Auth moves only with nk-auth, whose chain carries the schema each version needs; the guide states the rule and the order: bump, db:migrate against the target database, deploy.

Patch Changes

  • fed2c3c: Raise dependency floors: zod ^4.6.4, jose ^6.2.12, stripe ^22.6.2,
    intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
    oxfmt ^0.67 and knip ^6.35. No API change.

@ingram-tech/nk-i18n@0.6.0

Minor Changes

  • dbbe3e6: LocaleProvider is gone; @ingram-tech/nk-i18n/client exports LocaleContext instead. Render it as the provider, <LocaleContext value={locale}>, in a client or (React 19.3) server component. The React peer is now ^19.0.0, which <Context value> needs.

Patch Changes

  • fed2c3c: Raise dependency floors: zod ^4.6.4, jose ^6.2.12, stripe ^22.6.2,
    intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
    oxfmt ^0.67 and knip ^6.35. No API change.
  • c3554e1: Raise the react / react-dom peer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.

@ingram-tech/nk-billing@0.3.9

Patch Changes

  • fed2c3c: Raise dependency floors: zod ^4.6.4, jose ^6.2.12, stripe ^22.6.2,
    intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
    oxfmt ^0.67 and knip ^6.35. No API change.

@ingram-tech/nk-blog@0.1.11

Patch Changes

  • fed2c3c: Raise dependency floors: zod ^4.6.4, jose ^6.2.12, stripe ^22.6.2,
    intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
    oxfmt ^0.67 and knip ^6.35. No API change.
  • c3554e1: Raise the react / react-dom peer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.
  • Updated dependencies [c3554e1]
    • @ingram-tech/nk-seo@0.10.2

@ingram-tech/nk-db@2.1.3

Patch Changes

  • fed2c3c: Raise dependency floors: zod ^4.6.4, jose ^6.2.12, stripe ^22.6.2,
    intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
    oxfmt ^0.67 and knip ^6.35. No API change.

@ingram-tech/nk-forms@0.4.1

Patch Changes

  • c3554e1: Raise the react / react-dom peer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.
  • @ingram-tech/nk-email@0.6.2

@ingram-tech/nk-seo@0.10.2

Patch Changes

  • c3554e1: Raise the react / react-dom peer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.

@ingram-tech/nk-themes@0.2.4

Patch Changes

  • c3554e1: Raise the react / react-dom peer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.

@jleclanche
Jerome Leclanche (jleclanche) deleted the changeset-release/main branch September 13, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant