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

Patch Changes

• e6454f3: createAuthHelpers: memoize the validated session read per request with React cache(). A render fanning out many getUser() / requireUser() calls now validates the session against the database once per request instead of once per call (measured 9 → 1 on a financica page). Caveat: mutating the session mid-request and re-reading it through the helpers returns the pre-mutation snapshot; read auth.api.getSession directly in that case.
• Updated dependencies [af5209d]
  • @ingram-tech/nk-db@1.3.1

@ingram-tech/nk-db@1.3.1

Patch Changes

• af5209d: createPool no longer throws when no connection string is configured — it
  returns a pool that constructs cleanly and defers the "set DATABASE_URL" error
  to first use. Constructing the pool happens at module load in every app's
  lib/db, so importing that module (and therefore next build collecting page
  data, a unit test, or a CLI tool that never queries) must stay side-effect-free;
  a hard throw at construction broke DB-less builds. A process that then runs a
  real query without a URL still fails fast and legibly — the env is fixed at
  process start, so this is never a transient miss. The deferred rejection is
  async (a macrotask, like real connection I/O) so Next.js partial prerendering
  sees a pending promise and postpones the segment, instead of a synchronous
  render error. A present-but-invalid DATABASE_URL still throws eagerly.

@ingram-tech/nk-seo@0.6.1

Patch Changes

• 246e91d: createRobots now throws if a disallow entry would block /_next. Crawlers
  must fetch the JS/CSS under /_next to render pages, so disallowing it silently
  degrades indexing — Next.js does not block it by default and neither should a
  site. The guard is a prefix check (/_next, /_next/, _next/static, …); an
  unrelated prefix like /_preview is unaffected.