Version Packages - #54
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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_3relaxes the 1.7 account identity constraint 0002 set: the(issuer, accountId)unique index and the NOT NULL onaccount.issuerare 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-authand@better-auth/passkeyare pinned to exactly1.7.4inpeerDependencies. 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.createAuthHelperschecks the chain once per process, on the first session read: when the instance'sdatabaseis apgPool and the database records the nk-auth chain, a journal behind the installed package throws the newAuthChainNotAppliedErrornaming 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 forinstrumentation.tsor a health check;chainCheck: falseopts out.Patch Changes
intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
oxfmt ^0.67 and knip ^6.35. No API change.
createAuthMiddlewaredetects the session cookie undersessionCookiePrefix, not only the defaultbetter-authname. An app with its ownadvanced.cookiePrefixpreviously looped between the gate (no cookie seen) and the server guard (valid session).react/react-dompeer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.@ingram-tech/nk-dev@0.17.0
Minor Changes
nk doctorfails a site whosebetter-auth/@better-auth/passkeyis declared at any version or range other than the exact one the installed nk-auth pins in itspeerDependencies(--fixpins 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:migrateagainst the target database, deploy.Patch Changes
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
LocaleProvideris gone;@ingram-tech/nk-i18n/clientexportsLocaleContextinstead. 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
intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
oxfmt ^0.67 and knip ^6.35. No API change.
react/react-dompeer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.@ingram-tech/nk-billing@0.3.9
Patch Changes
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
intl-messageformat ^11.2.15; nk-dev's toolchain moves to oxlint ^1.82,
oxfmt ^0.67 and knip ^6.35. No API change.
react/react-dompeer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.@ingram-tech/nk-db@2.1.3
Patch Changes
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
react/react-dompeer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.@ingram-tech/nk-seo@0.10.2
Patch Changes
react/react-dompeer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.@ingram-tech/nk-themes@0.2.4
Patch Changes
react/react-dompeer floors to ^19.3.0 (additive release: ViewTransition, fragment refs, independent transitions). No API change.