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-forms@0.3.0

Minor Changes

• bdc28df: Absorb @ingram-tech/bot-protection into nk-forms. Nothing in the fleet
  depended on it directly — nk-forms was its only consumer and already re-exported
  its whole surface — so the separate package bought a second version number,
  changelog and release for 600 lines that were already an implementation detail.

  Additive for nk-forms: verifyHuman, checkBot, createFormToken,
  verifyFormToken, HONEYPOT_FIELD, TOKEN_FIELD and isConfigured now come
  from the root, with <HoneypotField> at /honeypot and the field names at
  /fields. BOT_PROTECTION_SECRET keeps its name, so no site config changes.
  botid becomes an optional peer dependency of nk-forms.

  Sites importing @ingram-tech/bot-protection directly (none known) should
  switch the specifier to @ingram-tech/nk-forms; that package is deprecated on
  npm.

@ingram-tech/nk-seo@0.10.0

Minor Changes

• a589e0b: nk-seo: createMetadata({ hreflang }) emits the locale cluster from metadata. Set it once on the site config (the nk-i18n routing object fits directly) and every pageMetadata() call gains alternates.languages (with x-default) and a canonical that follows the address; pass urlLocale on dynamic pages so a localized URL canonicalizes to itself. Because this goes through metadata rather than the x-pathname request header, it works on statically rendered routes (force-static), where <HreflangLinks> has no header to read and throws — the READMEs now say so and point at the metadata wiring as the preferred one. nk-i18n: docs only.

@ingram-tech/nk-blog@0.1.8

Patch Changes

• Updated dependencies [a589e0b]
  • @ingram-tech/nk-seo@0.10.0

@ingram-tech/nk-i18n@0.5.1

Patch Changes

• a589e0b: nk-seo: createMetadata({ hreflang }) emits the locale cluster from metadata. Set it once on the site config (the nk-i18n routing object fits directly) and every pageMetadata() call gains alternates.languages (with x-default) and a canonical that follows the address; pass urlLocale on dynamic pages so a localized URL canonicalizes to itself. Because this goes through metadata rather than the x-pathname request header, it works on statically rendered routes (force-static), where <HreflangLinks> has no header to read and throws — the READMEs now say so and point at the metadata wiring as the preferred one. nk-i18n: docs only.
• 8cb32be: LocaleRouting.hrefLangTags and hreflangConfigFor()'s result keep the locale union (L) instead of widening to string; still assignable to nk-seo's HreflangConfig.